SymfonyFramework / library · Sensiolabs
CVE-2026-45075
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 7.4.12 and 8.0.12, method-scoped #[IsGranted], #[IsSignatureValid], and #[IsCsrfTokenValid] attributes can be configured for GET only, but Symfony routes HEAD requests to the GET handler while the attribute check is skipped, allowing protected controllers to execute and leak headers or perform side effects. This issue is fixed in versions 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 confidenceIn Symfony prior to 7.4.12 and 8.0.12, method-scoped security attributes (#[IsGranted], #[IsSignatureValid], #[IsCsrfTokenValid]) configured only for GET requests can be bypassed via HEAD requests. Symfony routes HEAD requests to the GET handler but skips the security attribute check, allowing protected controllers to execute and potentially leak headers or perform side effects.
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
>= 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
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Determine installed Symfony versionRun 'composer show symfony/framework-bundle' or check the version in your composer.lock file under symfony/symfonyAffected if The version is >= 7.4.0 and < 7.4.12, or >= 8.0.0 and < 8.0.12
-
Identify controllers using method-scoped security attributesSearch your codebase for controller methods decorated with #[IsGranted], #[IsSignatureValid], or #[IsCsrfTokenValid] attributes. Look for patterns like '#\[(IsGranted|IsSignatureValid|IsCsrfTokenValid)\(' in PHP files under src/ or similar controller directories.Affected if Any of these attributes are present on controller methods that handle GET requests
-
Check if routes explicitly allow HEAD methodExamine your route definitions (in controller annotations, attributes, or YAML/XML config files) to see if HEAD is explicitly listed as an allowed method alongside GET, or if routes default to GET which implicitly accepts HEAD.Affected if Routes handling protected resources accept HEAD requests (which Symfony routes to GET handlers)
-
Test HEAD request bypassSend a HEAD request using curl -X HEAD to an endpoint protected by #[IsGranted], #[IsSignatureValid], or #[IsCsrfTokenValid] that is accessed via GET. Example: curl -X HEAD https://yourapp.com/protected-route -vAffected if The HEAD request returns a 2xx response instead of a 403 Forbidden, indicating the security check was skipped
You are affected if your Symfony version is within the vulnerable range AND you have security attributes on GET routes that accept HEAD requests, and HEAD requests to those endpoints bypass authentication.
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 · scoped7.4.128.0.12
Upgrade Symfony to version 7.4.12 or 8.0.12 or later to receive the patch that properly applies security attribute checks to HEAD requests routed through GET handlers.
Symfony 7.4.12 or 8.0.12
- Run composer require symfony/framework-bundle:^7.4.12 to update Symfony to version 7.4.12, or composer require symfony/framework-bundle:^8.0.12 for version 8.0.12
- Verify the version was updated by running composer show symfony/framework-bundle
- Test your application to ensure the security attributes (#[IsGranted], #[IsSignatureValid], #[IsCsrfTokenValid]) now correctly handle HEAD requests
- Ensure any HEAD-specific routes or controller logic works as expected after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Symfony
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45075 — 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-45075 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