Loading vulnerability…
Spring Security 7.0.0 through 7.0.4 contains an improper authentication vulnerability in SubjectX500PrincipalExtractor. The extractor does not correctly handle certain malformed X.509 certificate common-name values and can extract an incorrect value as the username. A carefully crafted client certificate can consequently cause Spring Security to associate authentication with another user identity.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a small Java/Maven proof-of-concept lab for CVE-2026-22747 in Spring Security X.509 authentication. Its purpose is twofold: (1) reproduce the vulnerable behavior in Spring Security Web 7.0.4, where SubjectX500PrincipalExtractor incorrectly extracts the first CN from a multi-CN DN string and enables user impersonation, and (2) demonstrate that version 6.5.10 is not affected by this specific CVE because the named vulnerable class does not exist in that branch. Repository structure: - run.sh is the main orchestrator. It downloads Spring Security Web JARs for 6.5.10, 7.0.4, and 7.0.5 from Maven Central, checks whether SubjectX500PrincipalExtractor.class exists in each JAR, generates a local CA and a crafted attacker certificate, runs Maven profiles, and writes report.txt. - pom.xml defines two Maven profiles: safe (Spring Security 6.5.10, runs CheckSafe, excludes CheckVuln) and vuln (Spring Security 7.0.4, runs CheckVuln, excludes CheckSafe). - CheckSafe.java loads certs/attacker.crt and uses SubjectDnX509PrincipalExtractor, the default 6.x extractor, to show behavior on the non-target branch. - CheckVuln.java loads the same certificate and uses SubjectX500PrincipalExtractor, the class explicitly tied to the CVE, to reproduce the impersonation condition. - security-log.yaml is a structured assessment log documenting affected versions, root cause, fix commit, evidence, and reproduction details. - README.md explains the vulnerability, affected range, mitigation guidance, and how to run the lab. Exploit capability: The repo does not deliver remote code execution or a shell. Instead, it demonstrates an authentication/identity confusion flaw. The crafted certificate subject O=attacker,CN=alice,CN=mallory causes the vulnerable extractor in 7.0.4 to return alice, even though the expected most-specific CN is mallory. In a real Spring Security X.509 deployment, this could let a client authenticate as another user if the application maps the extracted principal directly to an account. Operationally, this is a local proof-of-concept and validation harness rather than a weaponized exploit. It relies on local certificate generation and local execution of Java test code, but the underlying vulnerability affects network-facing web applications that use mutual TLS / X.509 client authentication with vulnerable Spring Security versions.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Spring Security 7.0.x vulnerability allowing unauthorized user impersonation when using X.509 client certificates, fixed in version 7.0.5.
A Spring Security vulnerability summarized as unauthorized user impersonation affecting X.509 certificates handling.
A Spring Security vulnerability that can allow unauthorized user impersonation when using X.509 client certificates.
A related earlier CVE that addressed the same X.509 client certificate user impersonation issue for Spring Security 7.0.x.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.