CVE-2026-97848 · Package
NO FIX YET
When a Keycloak protocol mapper emits structured JSON claims, the check that strips unauthorized role mappings does not recognize Jackson JSON objects. An attacker can inject forged client roles into security tokens and reach protected resources.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Organizations running Keycloak as their identity provider where a protocol mapper is configured to emit structured claims using the JSON type. Deployments that do not use such mappers are not described as affected by the sources. The sources do not name affected versions.
Not affected if no-json-protocol-mapper
Who cares identity, keycloak, self-hosted
Unknown from the sources.
No fix yet, per the sources.
A flaw was found in the token sanitization logic of Keycloak, an open source identity and access management solution. The issue occurs when a protocol mapper is configured to emit structured claims using the JSON type. The security check designed to remove unauthorized role mappings only looks for standard Java maps and fails to recognize Jackson based JSON objects. This allows an attacker to inject forged client roles into security tokens, which could lead to unauthorized access to protected resources.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.