CVE-2026-45075

Analyzed Analyzed - Analysis Complete

Symfony Framework Route Handling Security Bypass

Publication date: 2026-07-14

Last updated on: 2026-07-16

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-14

Last Modified

2026-07-16

Generated

2026-08-04

AI Q&A

2026-07-15

EPSS Evaluated

2026-08-02

NVD

CVE-2026-45075

EUVD

EUVD-2026-44350

Affected Vendors & Products

Vendor	Product	Version / Range
sensiolabs	symfony	From 8.0.0 (inc) to 8.0.12 (exc)
sensiolabs	symfony	From 7.4.0 (inc) to 7.4.12 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Executive Summary

This vulnerability affects Symfony versions 7.4 and 8.0. It involves security attributes like #[IsGranted] that restrict access to specific HTTP methods (e.g., GET). However, Symfony routes HEAD requests to the GET handler without enforcing these restrictions, allowing unauthorized access to protected endpoints.

Detection Guidance

To detect this vulnerability, check your Symfony application version with 'composer show symfony/symfony' or 'php bin/console --version'. If using versions 7.4.0 to 7.4.11 or 8.0.0 to 8.0.11, the system is vulnerable. Inspect routes with attributes like #[IsGranted], #[IsSignatureValid], or #[IsCsrfTokenValid] configured for GET only. Test endpoints with HEAD requests using tools like curl: 'curl -I http://yourdomain.com/protected-route' and verify if authorization checks are bypassed.

Impact Analysis

An attacker could exploit this by sending a HEAD request to a protected endpoint, bypassing security checks. This may lead to unauthorized actions like data leaks, database modifications, or other side effects triggered by the controller.

Compliance Impact

This vulnerability could lead to unauthorized access or data exposure, violating compliance requirements for data protection (e.g., GDPR, HIPAA). Unauthorized access may result in data breaches, triggering legal and regulatory penalties.

Mitigation Strategies

Immediately upgrade Symfony to versions 7.4.12 or 8.0.12 or later. If upgrading is not possible, modify route attributes to include HEAD in the methods option, e.g., 'methods: ['GET', 'HEAD']'. Review and update security configurations to ensure HEAD requests are handled with proper authorization checks.

Hi! I’m here to help you understand CVE-2026-45075. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70