Summary
Symfony's HEAD Request Bypasses methods: ['GET'] Filter in #[IsGranted] / #[IsSignatureValid] / #[IsCsrfTokenValid]
Description
Symfony's #[IsGranted('...')], #[IsSignatureValid], and #[IsCsrfTokenValid(...)] attributes allow you to define a methods: [...] argument to only enforce these checks for the listed HTTP methods and skip them otherwise. E.g. an attribute defining methods: ['GET'] would be ignored for a HEAD request.
On the other hand, Symfony's router (and HTTP semantics generally) serves HEAD requests using the GET handler. Therefore, a controller protected by e.g. #[IsGranted('ROLE_ADMIN', methods: ['GET'])] can be reached via HEAD with the authorization check silently skipped.
Even if the HEAD request won't get any response content, response headers leak (Content-Length, Location, custom headers). Also, the controller still executes and any side effects (DB writes, state changes) occur.
Resolution
When adding GET in the methods option of these attributes, Symfony now also include the HEAD method automatically.
The patch for this issue is available here for branch 7.4.
Credits
Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and Alexandre Daubois for fixing it.
Impact
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
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/http-kernel to 7.4.12 or later; symfony/http-kernel to 8.0.12 or later; symfony/security-http to 7.4.12 or later; symfony/security-http to 8.0.12 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-45075? CVE-2026-45075 is a high-severity incorrect authorization vulnerability in symfony/http-kernel (composer), affecting versions >= 7.4.0, < 7.4.12. It is fixed in 7.4.12, 8.0.12. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which packages are affected by CVE-2026-45075?
symfony/http-kernel(composer) (versions >= 7.4.0, < 7.4.12)symfony/security-http(composer) (versions >= 7.4.0, < 7.4.12)symfony/symfony(composer) (versions >= 7.4.0, < 7.4.12)
- Is there a fix for CVE-2026-45075? Yes. CVE-2026-45075 is fixed in 7.4.12, 8.0.12. Upgrade to this version or later.
- Is CVE-2026-45075 exploitable, and should I be worried? Whether CVE-2026-45075 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-45075 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-45075?
- Upgrade
symfony/http-kernelto 7.4.12 or later - Upgrade
symfony/http-kernelto 8.0.12 or later - Upgrade
symfony/security-httpto 7.4.12 or later - Upgrade
symfony/security-httpto 8.0.12 or later - Upgrade
symfony/symfonyto 7.4.12 or later - Upgrade
symfony/symfonyto 8.0.12 or later
- Upgrade