Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-118513

Authentication bypass by spoofing inX509AuthenticatorandX509Authentica ...

Overview

Published
4 Nov 2026
Modified
6 Nov 2026
High CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available
CVSS score High, no score

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.

Source: OX vulnerability database

Severity

HIGH

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-290

Affected packages · 2

Packages affected by CVE-2026-118513
EcosystemPackageVulnerableFixed in
Composer (PHP) symfony/security-http >=5.3.0, <5.4.0>=6.0.0, <6.1.0>=7.4.0, <7.4.23>=7.0.0, <7.1.0>=3.0.0, <4.0.0+15 more No fix yet
Composer (PHP) symfony/symfony >=6.1.0, <6.2.0>=7.1.0, <7.2.0>=8.0.0, <8.1.0>=7.0.0, <7.1.0>=3.0.0, <4.0.0+15 more No fix yet

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

debian 4 releases · 1 package

affected 2 fixed 2
symfony
debian fixes for CVE-2026-118513
ReleasePackageFixed in
11 symfony affected
12 symfony affected
13 symfony 6.4.50+dfsg-0+deb13u1
14 symfony 7.4.23+dfsg-1

echo 1 release · 1 package

fixed 1
symfony
echo fixes for CVE-2026-118513
ReleasePackageFixed in
symfony 6.4.50+dfsg-0+deb13u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.