Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-45075 – Authorization Bypass via HEAD Request – Symfony 7.4.0–7.4.11 and 8.0.0–8.0.11

Be the first to know when new zero-days emerge:

Summary

CVE-2026-45075 is a high-severity authorization bypass vulnerability in Symfony, a widely-used PHP web application framework. When method-scoped security attributes (#[IsGranted], #[IsSignatureValid], #[IsCsrfTokenValid]) are configured to restrict checks to GET requests, an unauthenticated attacker can send an HTTP HEAD request to silently bypass the security check and reach the protected controller. The vulnerability is rated 8.3 (CVSS 4.0 / HIGH) and is classified under CWE-863: Incorrect Authorization.

Technical details

  • Root cause: Symfony’s router forwards HEAD requests to GET handlers as required by HTTP semantics. However, when the optional methods: ['GET'] argument is used in a security attribute, the corresponding authorization check does not automatically extend to HEAD requests — causing it to be silently skipped rather than failing securely.
  • Trigger conditions: The vulnerability only exists when controllers are decorated with #[IsGranted], #[IsSignatureValid], or #[IsCsrfTokenValid] using the optional methods: [...] argument scoped to GET. Controllers that use these attributes without method scoping are not affected.
  • Attack vector: Unauthenticated, fully remote. An attacker sends a crafted HTTP HEAD request to a protected endpoint — no credentials, session token, or prior access required.
  • Impact:
    • Authorization controls are silently bypassed, granting unauthenticated access to protected controller logic.
    • Response headers (e.g., Content-Length, Location, custom application headers) are returned, potentially leaking sensitive metadata about protected resources.
    • All controller side effects — including database writes, state mutations, and downstream operations — execute normally despite the absent authorization check.

Affected software

  • symfony/symfony and symfony/security-http: versions ≥ 7.4.0 and < 7.4.12
  • symfony/symfony and symfony/security-http: versions ≥ 8.0.0 and < 8.0.12

Severity

  • CVSS 4.0: 8.3 (HIGH) — 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
  • CVSS 3.1: 8.1 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
  • CWE: CWE-863 (Incorrect Authorization)

Mitigation and recommended actions

  • Immediate — apply vendor patch: Upgrade Symfony to 7.4.12 or 8.0.12 (or any later release). The fix ensures that when GET is listed in the methods option of a security attribute, HEAD requests are automatically subject to the same authorization check.
  • If immediate patching is not feasible: Audit your application for any controller using #[IsGranted], #[IsSignatureValid], or #[IsCsrfTokenValid] with a methods: [...] argument. For sensitive endpoints, consider temporarily blocking or restricting HEAD requests at the web server or reverse proxy layer (e.g., via nginx limit_except directives or Apache LimitExcept blocks) until the patch can be applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge