CVE-2026-118513
Received Received - Intake

Authentication Bypass via X509Authenticator in Symfony

Vulnerability report for CVE-2026-118513, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-04

Last updated on: 2026-11-04

Assigner: Checkmarx

Description

Authentication bypass by spoofing in X509Authenticator and X509AuthenticationListener of Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11 allows an attacker holding a certificate from the application's trusted CA who can influence the CN to authenticate as an arbitrary user of the application, including a privileged one, following an incomplete fix for CVE-2026-45063. X509Authenticator extracts the user identifier from the Subject DN (Distinguished Name) that the web server passes in $_SERVER['SSL_CLIENT_S_DN']. The fix for CVE-2026-45063 anchored that extraction to an RDN (Relative Distinguished Name) boundary, but the regular expression used was not escape-aware. The expression runs against an already serialized DN, so it cannot tell an RDN separator from a separator character that occurs inside a value. Under RFC 2253, used by Apache and by nginx's $ssl_client_s_dn, a comma inside a value is escaped as \, and the expression reads it as a separator regardless. RFC 2253 also does not treat / as a separator, so it leaves it bare inside a value, while the expression treats every / as one. The legacy X509_NAME_oneline() format, used by Apache's LegacyDNStringFormat and by nginx's $ssl_client_s_dn_legacy, is the mirror image: it escapes / as \/ and leaves , bare. In that format, a certificate with no emailAddress attribute, or whose poisoned CN precedes it, authenticates as the smuggled address. To cover both RFC 2253 and the legacy X509_NAME_oneline() format, X509Authenticator and X509AuthenticationListener now split the DN into RDNs before looking for the attribute, instead of matching the attribute against the serialized string. They select the separator from the serialization, split on unescaped occurrences of that separator only, unescape each RDN afterwards with the rules of its format, and require the attribute to span a whole RDN. The accepted value grammar is unchanged. Applications that pass a per-attribute user key (such as SSL_CLIENT_S_DN_Email) and deployments whose CA generates or validates the subject are not affected by this vulnerability.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-04
Last Modified
2026-11-04
Generated
2026-11-04
AI Q&A
2026-11-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-290 This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an authentication bypass in Symfony's X509Authenticator and X509AuthenticationListener components. It allows an attacker with a certificate from the application's trusted CA to manipulate the Common Name (CN) field to impersonate any user, including privileged ones. The issue stems from improper parsing of Distinguished Names (DNs) in X.509 certificates, where escaped characters like commas or slashes within attribute values were incorrectly treated as separators.

Detection Guidance

To detect this vulnerability, inspect Symfony applications using X509Authenticator or X509AuthenticationListener for improper DN parsing. Check if the application is running vulnerable versions (Symfony <5.4.56, <6.4.50, <7.4.23, or <8.1.11). Review certificate handling in web server configurations (Apache/nginx) for RFC 2253 or legacy DN formats.

Impact Analysis

An attacker could exploit this to gain unauthorized access to the application as any user, including administrators. This could lead to data breaches, privilege escalation, or unauthorized actions within the system. The impact depends on the application's user roles and permissions.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. It may result in non-compliance due to potential data breaches, unauthorized access to protected health information, or failure to implement proper authentication controls.

Mitigation Strategies

Upgrade Symfony to patched versions (5.4.56, 6.4.50, 7.4.23, or 8.1.11+). If using legacy DN formats with OpenSSL <3.0 or HAProxy, switch to RFC 2253 output or per-attribute user keys (e.g., SSL_CLIENT_S_DN_Email). Ensure CA validates subject fields to prevent spoofing.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-118513. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...