Symfony's HEAD Request Bypasses methods: ['GET'] Filter in #[IsGranted] / #[IsSignatureValid] / #[IsCsrfTokenValid]
Published 27 May 2026 · Updated 10 Sept 2026
Is your project on an affected symfony/http-kernel?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=7.4.0 <7.4.12
- Fixed in
- 7.4.12
composer require symfony/http-kernel:^7.4.12- Affected
- >=8.0.0 <8.0.12
- Fixed in
- 8.0.12
composer require symfony/http-kernel:^8.0.12- Affected
- >=7.4.0 <7.4.12
- Fixed in
- 7.4.12
composer require symfony/security-http:^7.4.12- Affected
- >=8.0.0 <8.0.12
- Fixed in
- 8.0.12
composer require symfony/security-http:^8.0.12- Affected
- >=7.4.0 <7.4.12
- Fixed in
- 7.4.12
composer require symfony/symfony:^7.4.12- Affected
- >=8.0.0 <8.0.12
- Fixed in
- 8.0.12
composer require symfony/symfony:^8.0.12Details
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.
Is GHSA-6439-2f28-8p8q in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/http-kernel, and gives you the command that fixes it.
More advisories for symfony/http-kernel
- HighCVE-2014-5245Symfony allows direct access of ESI URLs behind a trusted proxy · 30 May 2024
- MediumCVE-2022-24894Symfony storing cookie headers in HttpCache · 1 Feb 2023
- MediumCVE-2015-2308Symfony Vulnerable to PHP Eval Injection · 17 May 2022
- MediumCVE-2015-4050Symfony Incorrect Access Control · 17 May 2022
- HighCVE-2019-18887Symfony Http-Kernel has non-constant time comparison in UriSigner · 26 Mar 2022
- MediumCVE-2021-41267Webcache Poisoning in symfony/http-kernel · 24 Nov 2021
References
- Linkgithub.com/symfony/symfony/security/advisories/GHSA-6439-2f28-8p8q
- Linkgithub.com/symfony/symfony/commit/fa8d5c67aa4b22c9656e3fd7d5c3aa59865bf838
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/http-kernel/CVE-2026-45075.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-http/CVE-2026-45075.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2026-45075.yaml
- Packagegithub.com/symfony/symfony
- Linksymfony.com/cve-2026-45075
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.