How severe is CVE-2026-45069?

No CVSS score has been assigned to CVE-2026-45069 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-45069?

CVE-2026-45069 affects the following packages: symfony/security-http (Packagist), symfony/security-http (Packagist), symfony/security-http (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-45069?

Update symfony/security-http to 6.4.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45069 is resolved across your whole dependency graph.

How do I detect CVE-2026-45069 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-45069 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-45069 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-45069 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-45069?

CVE-2026-45069 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-45069?

CVE-2026-45069 is classified as CWE-345 (CWE-345), CWE-1287 (CWE-1287). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-45069 published, and has it been updated?

CVE-2026-45069 was published on July 14, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-45069 — security-http

Fix: symfony/symfony@6b717aa

CVE-2026-45069 is a CWE-345 vulnerability in symfony/security-http. A fix is available for symfony/security-http — see the affected versions and patch details below.

Symfony: OidcTokenHandler Accepts JWTs Missing aud/iss/exp Claims

Also known asGHSA-29fc-p6c4-24cg

Published

Jul 14, 2026

Updated

Aug 12, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-45069.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

6 pkgs affected

🐘symfony/security-http🐘symfony/security-http🐘symfony/security-http🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/security-http`	≥ 6.3.0&&< 6.4.40	6.4.40`composer require symfony/security-http:^6.4.40`
🐘Packagist	`symfony/security-http`	≥ 7.4.0&&< 7.4.12	7.4.12`composer require symfony/security-http:^7.4.12`
🐘Packagist	`symfony/security-http`	≥ 8.0.0&&< 8.0.12	8.0.12`composer require symfony/security-http:^8.0.12`
🐘Packagist	`symfony/symfony`	≥ 6.3.0&&< 6.4.40	6.4.40`composer require symfony/symfony:^6.4.40`
🐘Packagist	`symfony/symfony`	≥ 7.4.0&&< 7.4.12	7.4.12`composer require symfony/symfony:^7.4.12`
🐘Packagist	`symfony/symfony`	≥ 8.0.0&&< 8.0.12	8.0.12`composer require symfony/symfony:^8.0.12`

Affected Products

1 product · 3 configurations

Application

symfonysensiolabs

≥ 8.0.0 && < 8.0.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/security-http to 6.4.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45069 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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