CVE-2026-45075: Symfony: 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('ROLEADMIN', 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.
Other sources
Symfony 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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/symfony/symfonyto a version that resolves this vulnerability.Fixed in 8.0.12 - Upgrade
Upgrade
composer/symfony/symfonyto a version that resolves this vulnerability.Fixed in 7.4.12 - Upgrade
Upgrade
composer/symfony/security-httpto a version that resolves this vulnerability.Fixed in 8.0.12 - Upgrade
Upgrade
composer/symfony/security-httpto a version that resolves this vulnerability.Fixed in 7.4.12 - Upgrade
Upgrade
composer/symfony/http-kernelto a version that resolves this vulnerability.Fixed in 8.0.12 - Upgrade
Upgrade
composer/symfony/http-kernelto a version that resolves this vulnerability.Fixed in 7.4.12 - Upgrade
Upgrade
Symfonyto a version that resolves this vulnerability.Fixed in 7.4.12 - Upgrade
Upgrade
Symfonyto a version that resolves this vulnerability.Fixed in 8.0.12
Event History
Frequently Asked Questions
What is the severity of CVE-2026-45075?
CVE-2026-45075 has a risk rating of 65.
How do I fix CVE-2026-45075?
To fix CVE-2026-45075, ensure that you properly configure your Symfony attributes and review the HTTP methods that are being used.
What vulnerabilities are associated with CVE-2026-45075?
CVE-2026-45075 is associated with vulnerabilities related to CSRF in Symfony's security attributes.
Which versions of Symfony are affected by CVE-2026-45075?
CVE-2026-45075 affects several versions of Symfony, including symfony/security-http and symfony/http-kernel.
Are there any mitigation strategies for CVE-2026-45075?
Mitigation strategies for CVE-2026-45075 include restricting the use of method arguments in security attributes and validating CSRF tokens diligently.