Skip to content
major vulnerability· requires attention

Affects widely used Keycloak; token forgery via IdP signing key can bypass access controls, impacting many orgs.

Web

CVE-2026-1486

8.8
High
EPSS 0.46%Patch availableFeb 10, 2026

Keycloak token issuance flaw enables forging JWTs with disabled IdP signing key.

common questions

Is CVE-2026-1486 being exploited?

Not confirmed. CVE-2026-1486 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-1486?

CVE-2026-1486 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-1486?

Yes. A fix has been recorded for CVE-2026-1486. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-1486 affect?

CVE-2026-1486 affects Keycloak. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-1486?

Patch Keycloak; rotate IdP signing keys; review IdP configurations.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Keycloak
impact

Attacker with IdP signing key can obtain valid access tokens despite IdP being disabled.

action required

Patch when possible

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free