SymfonyFramework / library · Sensiolabs
CVE-2026-45069
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSymfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 6.4.40, 7.4.12, and 8.0.12, OidcTokenHandler::verifyClaims() registered audience (aud), issuer (iss), and expiry (exp) checkers but did not pass the mandatory claims list to ClaimCheckerManager::check(), so a validly signed JWT that omitted those claims could pass verification. This issue is fixed in versions 6.4.40, 7.4.12, and 8.0.12.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OidcTokenHandler::verifyClaims() method in Symfony registered claim checkers for audience (aud), issuer (iss), and expiry (exp) but failed to pass the mandatory claims list to ClaimCheckerManager::check(), allowing validly signed JWTs that omitted these required claims to pass verification, enabling authentication bypass.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SymfonyFramework / library
>= 6.3.0, < 6.4.40>= 7.4.0, < 7.4.12>= 8.0.0, < 8.0.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Symfony framework versionRun `composer show symfony/framework-bundle 2>/dev/null | grep version` or check your composer.lock file for the symfony/framework-bundle versionAffected if The installed version falls within >= 6.3.0, < 6.4.40 OR >= 7.4.0, < 7.4.12 OR >= 8.0.0, < 8.0.12
-
Verify OIDC token handling is in useSearch your codebase for OidcTokenHandler usage: grep -r "OidcTokenHandler" vendor/ or look for OIDC-related configuration in your security.yaml filesAffected if Your application uses OidcTokenHandler for JWT/OIDC token validation
-
Confirm JWT authentication is configuredReview your security configuration (security.yaml or security.php) for oauth2, jwt, or oidc firewalls and providersAffected if You have JWT-based or OIDC-based authentication configured for any firewall
-
Inspect token verification flowCheck the vendor code for Symfony\Security\OAuth\OidcTokenHandler or equivalent path and verify that ClaimCheckerManager::check() is called without a mandatory claims argumentAffected if The code path shows ClaimCheckerManager::check() is invoked without passing the mandatory claims list (aud, iss, exp)
You are affected if your Symfony version is within the affected ranges AND your application uses OIDC/JWT authentication via OidcTokenHandler without mandatory claim validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.4.407.4.128.0.12
Upgrade Symfony to versions 6.4.40, 7.4.12, or 8.0.12 or later to enforce proper mandatory claims validation in OIDC token handling.
Symfony 6.4.40, 7.4.12, or 8.0.12 depending on your major version branch
- Identify the current Symfony version by checking composer.json or running `composer show symfony/framework-bundle`
- Run `composer require symfony/framework-bundle:6.4.40 --no-interaction` for 6.3.x-6.4.x installations, `composer require symfony/framework-bundle:7.4.12 --no-interaction` for 7.4.x, or `composer require symfony/framework-bundle:8.0.12 --no-interaction` for 8.0.x
- Run `composer update symfony/framework-bundle --with-all-dependencies` to update the bundle and its dependencies
- Verify the upgrade was successful by running `composer show symfony/framework-bundle` and confirming the version number
- Test the OIDC authentication flow to confirm JWT claim verification works correctly with aud, iss, and exp claims
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Symfony
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45069 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data