CVE-2026-45075: Symfony: HEAD Request Bypasses methods: ['GET'] Filter in #[IsGranted] / #[IsSignatureValid] / #[IsCsrfTokenValid]
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: symfony (Debian:14) 7.4.12+dfsg-1; symfony/http-kernel (Packagist) 7.4.12, 8.0.12; symfony/security-http (Packagist) 7.4.12, 8.0.12.
Low priority for now. Upgrade to symfony (Debian:14) 7.4.12+dfsg-1; symfony/http-kernel (Packagist) 7.4.12, 8.0.12; symfony/security-http (Packagist) 7.4.12, 8.0.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 14, 2026
- Updated
- Jul 16, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-863
Report tools
Action score
33
Low priority for now.
- CVSS
- 33 / 40 · 8.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sensiolabs | symfony | cpe:2.3:a:sensiolabs:symfony |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
symfony http-kernel
- >= 7.4.0-BETA1, < 7.4.12, >= 8.0.0-BETA1, < 8.0.12affected
symfony security-http
- >= 7.4.0-BETA1, < 7.4.12, >= 8.0.0-BETA1, < 8.0.12affected
symfony symfony
- >= 7.4.0-BETA1, < 7.4.12, >= 8.0.0-BETA1, < 8.0.12affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sensiolabs symfony7.4.0 and later · before 7.4.12
- sensiolabs symfony8.0.0 and later · before 8.0.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | symfony | before 7.4.12+dfsg-1 | 7.4.12+dfsg-1 |
| Packagist | symfony/http-kernel | from 7.4.0 · before 7.4.12 | 7.4.12 |
| Packagist | symfony/http-kernel | from 8.0.0 · before 8.0.12 | 8.0.12 |
| Packagist | symfony/security-http | from 7.4.0 · before 7.4.12 | 7.4.12 |
| Packagist | symfony/security-http | from 8.0.0 · before 8.0.12 | 8.0.12 |
| Packagist | symfony/symfony | from 7.4.0 · before 7.4.12 | 7.4.12 |
| Packagist | symfony/symfony | from 8.0.0 · before 8.0.12 | 8.0.12 |
Same product
sensiolabs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-18889An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7.49Plan
- CVE-2018-14773An issue was discovered in Http Foundation in Symfony 2.7.0 through 2.7.48, 2.8.0 through 2.8.43, 3.3.0 through 3.3.17, 3.4.0 through…43Plan
- CVE-2019-10910In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, when service ids allow user…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-45070Jul 14, 2026 · Symfony: Email Header Injection via Non-Token Characters in Mime Parameter Names25Monitor
- ← EarlierCVE-2026-45072Jul 14, 2026 · Symfony: Stored XSS in WebProfiler CodeExtension::fileExcerpt() — Unescaped Non-PHP File Rendering8Monitor
- Later →CVE-2026-45133Jul 14, 2026 · Symfony: [Yaml] Harden the parser when handling untrusted input32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:symfony | 7.4.12+dfsg-1 · Debian:14 | Package registry (OSV) |
| Packagist:symfony/http-kernel | 7.4.12 | Package registry (OSV) |
| Packagist:symfony/http-kernel | 8.0.12 | Package registry (OSV) |
| Packagist:symfony/security-http | 7.4.12 | Package registry (OSV) |
| Packagist:symfony/security-http | 8.0.12 | Package registry (OSV) |
| Packagist:symfony/symfony | 7.4.12 | Package registry (OSV) |
| Packagist:symfony/symfony | 8.0.12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-484890 days apartSymfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes34Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.