CVE-2026-45063: Symfony: Identity Spoofing via Unanchored DN Regex in X509Authenticator

Published May 27, 2026
·
Updated

Description

X509Authenticator implements client-certificate (mTLS) authentication: the web server validates the client's certificate against a trusted CA, then passes the certificate's Subject DN (Distinguished Name: a string like CN=Alice,O=Example,emailAddress=alice@example.com) to Symfony via $SERVER['SSLCLIENTSDN']. Symfony extracts the user identifier from that string.

The extraction uses an unanchored regex that matches emailAddress= anywhere in the DN string: including inside the value of a different RDN (Relative Distinguished Name: one key=value component of the DN), such as CN. An attacker who can obtain a certificate from a trusted CA with a free-text CN can smuggle emailAddress=victim@target inside the CN value and be authenticated as the victim.

Resolution

The X509Authenticator now uses a regex that anchors the match to an RDN boundary (start of string, or following a , / / separator).

The patch for this issue is available here for branch 5.4.

Credits

Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and providing the fix.

Other sources

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, X509Authenticator extracts the user identifier from $SERVER['SSLCLIENTSDN'] with an unanchored regex that matches emailAddress= anywhere in the distinguished name, allowing an attacker with a trusted certificate containing emailAddress=victim inside another RDN value such as CN to authenticate as the victim. This issue is fixed in versions 5.4.52, 6.4.40, 7.4.12, and 8.0.12.

MITRE

Affected Software

12 affected componentsFixes available
composer/symfony/symfony>=8.0.0-BETA1<8.0.12
8.0.12
composer/symfony/symfony>=7.0.0-BETA1<7.4.12
7.4.12
composer/symfony/symfony>=6.0.0-BETA1<6.4.40
6.4.40
composer/symfony/symfony<5.4.52
5.4.52
composer/symfony/security-http>=8.0.0-BETA1<8.0.12
8.0.12
composer/symfony/security-http>=7.0.0-BETA1<7.4.12
7.4.12
composer/symfony/security-http>=6.0.0-BETA1<6.4.40
6.4.40
composer/symfony/security-http<5.4.52
5.4.52
SensioLabs Symfony<5.4.52
SensioLabs Symfony>=6.0.0<6.4.40
SensioLabs Symfony>=7.0.0<7.4.12
SensioLabs Symfony>=8.0.0<8.0.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 8.0.12
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 7.4.12
  3. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 6.4.40
  4. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 5.4.52
  5. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 8.0.12
  6. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 7.4.12
  7. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 6.4.40
  8. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 5.4.52
  9. Upgrade

    Upgrade Symfony X509Authenticator (client-certificate/mTLS) to a version that resolves this vulnerability.

    Fixed in 5.4.52Patch ccb3f724c7ff55670a6fe3521c7bf1514cceb478
  10. Upgrade

    Upgrade Symfony X509Authenticator (client-certificate/mTLS) to a version that resolves this vulnerability.

    Fixed in 6.4.40
  11. Upgrade

    Upgrade Symfony X509Authenticator (client-certificate/mTLS) to a version that resolves this vulnerability.

    Fixed in 7.4.12
  12. Upgrade

    Upgrade Symfony X509Authenticator (client-certificate/mTLS) to a version that resolves this vulnerability.

    Fixed in 8.0.12

Event History

May 27, 2026
Advisory Published
via GitHub·04:50 PM
Data Sourced
via GitHub·04:50 PM
DescriptionWeaknessAffected Software
Jul 14, 2026
CVE Published
via MITRE·06:28 PM
Data Sourced
via MITRE·06:28 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-45063?

CVE-2026-45063 is rated with a risk score of 55, indicating a moderate severity level.

2

What is the primary issue associated with CVE-2026-45063?

CVE-2026-45063 relates to the implementation of client-certificate authentication in X509Authenticator, which may expose applications to certain security risks.

3

How do I fix CVE-2026-45063?

To mitigate CVE-2026-45063, update your Symfony components to the latest versions where the vulnerability is addressed.

4

Is CVE-2026-45063 exploitable remotely?

Yes, CVE-2026-45063 can potentially be exploited remotely due to its connection with client-certificate authentication.

5

Which Symfony versions are impacted by CVE-2026-45063?

CVE-2026-45063 affects specific versions of Symfony, particularly those that utilize the X509Authenticator for client-certificate authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203