dbcve.org
Spring SecurityFramework / library · VMware

CVE-2026-22747

HIGH · 8.1 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 7.0.5 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in Spring Spring Security. SubjectX500PrincipalExtractor does not correctly handle certain malformed X.509 certificate CN values, which can lead to reading the wrong value for the username. In a carefully crafted certificate, this can lead to an attacker impersonating another user. This issue affects Spring Security: from 7.0.0 through 7.0.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SubjectX500PrincipalExtractor in Spring Security 7.0.0-7.0.4 fails to properly validate malformed X.509 certificate CN (Common Name) values. When processing a specially crafted certificate, the extractor reads an incorrect username value from the CN field, enabling an attacker to impersonate other users by presenting a manipulated certificate.

MitigationUpgrade Spring Security to version 7.0.5 or later to obtain the patch. As a temporary workaround, implement additional validation of X.509 certificate CN values at the application layer before using them for authentication decisions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring SecurityFramework / library
Affected:>= 7.0.0, < 7.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Spring Security version in use
    Inspect your project's dependency management file (Maven pom.xml, Gradle build.gradle, or similar) for the spring-security-version or org.springframework.security dependency version
    Affected if The version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.4 (any version >= 7.0.0 and < 7.0.5)
  2. Confirm X.509 certificate authentication is enabled
    Search your Spring Security configuration for references to X509CertificateAuthenticationToken, x509(), or certificate-based authentication configuration
    Affected if X.509 certificate authentication is explicitly configured and active in your security configuration
  3. Verify SubjectX500PrincipalExtractor is in use
    Search your codebase for any Bean definitions, XML configurations, or Java configuration classes that reference SubjectX500PrincipalExtractor or set a principal extractor for X.509 authentication
    Affected if SubjectX500PrincipalExtractor is configured as the principal extractor for X.509 authentication
  4. Check for CN validation logic
    Review your principal extractor configuration and any custom code that processes the CN (Common Name) from X.509 certificates to see if explicit validation exists
    Affected if No explicit CN validation is implemented before using the extracted CN for authentication purposes

You are affected if your application runs Spring Security version 7.0.0 through 7.0.4, uses X.509 certificate-based authentication with SubjectX500PrincipalExtractor, and lacks explicit validation of the certificate Common Name before authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.5 or later
Fixed in 7.0.5
Interim mitigation

Upgrade Spring Security to version 7.0.5 or later to obtain the patch. As a temporary workaround, implement additional validation of X.509 certificate CN values at the application layer before using them for authentication decisions.

Recommended fix High confidence

Spring Security 7.0.5 or later (recommended: latest 7.0.x stable release)

  1. Identify the current Spring Security version in your project (check pom.xml, build.gradle, or lock files)
  2. Upgrade Spring Security to version 7.0.5 or later by updating the dependency version in your build configuration
  3. Run your project's build to resolve the new dependency version
  4. Verify the upgrade by running your test suite, particularly any X.509 authentication tests
  5. Test the SubjectX500PrincipalExtractor functionality to ensure certificate CN extraction works correctly with the patched version
Caveat Review Spring Security 7.0.5 release notes for any breaking changes; minor version upgrades in the 7.0.x line typically have minimal breaking changes but always verify compatibility with your specific configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22747 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data