Summary
Symfony's OidcTokenHandler Accepts JWTs Missing aud/iss/exp Claims
Description
OidcTokenHandler is Symfony's built-in access-token handler for OpenID Connect: it validates a bearer JWT and returns the authenticated user identity. It delegates claim validation to the web-token/jwt-checker library's ClaimCheckerManager.
OidcTokenHandler::verifyClaims() registers audience (aud), issuer (iss), and expiry (exp) checkers, but never passes the $mandatoryClaims argument to ClaimCheckerManager::check(). That method only validates claims that are present in the token: a checker for an absent claim is silently skipped. A validly-signed JWT that simply omits aud, iss, and exp therefore passes verification.
Resolution
The OidcTokenHandler now calls the ClaimCheckerManager with the list of mandatory claims so that tokens missing aud, iss, or exp are rejected.
The patch for this issue is available here for branch 6.4.
Credits
Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and providing the fix.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
symfony/security-http to 6.4.40 or later; symfony/security-http to 7.4.12 or later; symfony/security-http to 8.0.12 or later; symfony/symfony to 6.4.40 or later; symfony/symfony to 7.4.12 or later; symfony/symfony to 8.0.12 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-45069? CVE-2026-45069 is a medium-severity security vulnerability in symfony/security-http (composer), affecting versions >= 6.3.0, < 6.4.40. It is fixed in 6.4.40, 7.4.12, 8.0.12.
- Which packages are affected by CVE-2026-45069?
symfony/security-http(composer) (versions >= 6.3.0, < 6.4.40)symfony/symfony(composer) (versions >= 6.3.0, < 6.4.40)
- Is there a fix for CVE-2026-45069? Yes. CVE-2026-45069 is fixed in 6.4.40, 7.4.12, 8.0.12. Upgrade to this version or later.
- Is CVE-2026-45069 exploitable, and should I be worried? Whether CVE-2026-45069 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-45069 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-45069?
- Upgrade
symfony/security-httpto 6.4.40 or later - Upgrade
symfony/security-httpto 7.4.12 or later - Upgrade
symfony/security-httpto 8.0.12 or later - Upgrade
symfony/symfonyto 6.4.40 or later - Upgrade
symfony/symfonyto 7.4.12 or later - Upgrade
symfony/symfonyto 8.0.12 or later
- Upgrade