Skip to main content
VulnerabilityPublished Updated

CVE-2026-45075: Http kernel · Symfony's HEAD Request Bypasses methods: ['GET'] Filter in #[IsGranted] / #[IsSignatureValid] / #[IsCsrfTokenValid]

Affects symfony/http-kernelSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 7.4.12 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.4.12, 8.0.12
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade symfony/http-kernel and symfony/security-http and symfony/symfony to 7.4.12; symfony/http-kernel and symfony/security-http and symfony/symfony to 8.0.12.

Affected software

ProductAffectedFixed in
Packagistsymfony/http-kernelAffected
  • >=7.4.0 <7.4.12
Fixed in
  • 7.4.12
Packagistsymfony/http-kernelAffected
  • >=8.0.0 <8.0.12
Fixed in
  • 8.0.12
Packagistsymfony/security-httpAffected
  • >=7.4.0 <7.4.12
Fixed in
  • 7.4.12
Packagistsymfony/security-httpAffected
  • >=8.0.0 <8.0.12
Fixed in
  • 8.0.12
Packagistsymfony/symfonyAffected
  • >=7.4.0 <7.4.12
Fixed in
  • 7.4.12
Packagistsymfony/symfonyAffected
  • >=8.0.0 <8.0.12
Fixed in
  • 8.0.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied to upgrade Symfony to versions >=7.4.12 or >=8.0.12 where the issue is fixed. The patch automatically includes HEAD when GET is specified in the methods argument of the affected attributes. Until patched, avoid restricting methods to GET only or explicitly include HEAD in the methods list to ensure checks are enforced on HEAD requests.

Description

### 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](https://github.com/symfony/symfony/commit/fa8d5c67aa4b22c9656e3fd7d5c3aa59865bf838) 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.

References

Community reviews

Loading reviews…