Security readout for executives and security teams
Plain-English summary
This flaw can let a user with a specially malformed client certificate be recognized as a different user. It matters most where Spring Security uses X.509 client certificates for login and maps the certificate CN to the application username.
Executive priority
Treat as high priority for mTLS or certificate-login applications because successful abuse could become account impersonation. Prioritize internet-facing, partner-facing, and privileged-user portals first.
Technical view
Spring Security 7.0.0 through 7.0.4 mishandles some malformed X.509 certificate CN values in SubjectX500PrincipalExtractor. The parser may read the wrong CN-derived username, creating an impersonation risk with high confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to applications on Spring Security 7.0.0-7.0.4 that use X.509 client certificate authentication with CN-based username extraction. Deployments not using that authentication path are less likely affected based on the provided sources.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. The CVSS vector indicates network reachability, low attack complexity, no user interaction, and low privileges required.
Researcher notes
Evidence supports a parser or name-extraction flaw in SubjectX500PrincipalExtractor, mapped to CWE-295 and CWE-297. The bundle does not include exploit details, confirmed exploitation, or a specific fixed version, so remediation should follow Spring guidance.
Mitigation direction
- Check the Spring advisory for the vendor-named fixed release or workaround.
- Inventory Spring Security versions and prioritize 7.0.0 through 7.0.4.
- Review X.509 authentication paths that rely on certificate CN username extraction.
- Temporarily tighten client-certificate issuance and identity mapping controls.
- Monitor authentication logs for unexpected certificate-subject to username mappings.
Validation and detection
- Confirm whether applications use Spring Security 7.0.0 through 7.0.4.
- Identify use of SubjectX500PrincipalExtractor or CN-based X.509 principal extraction.
- Review authentication tests for malformed certificate subject handling without adding exploit detail.
- Check certificate enrollment controls for who can obtain client certificates.
- Look for login events where certificate identity and application account differ unexpectedly.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-297: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22747 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2redhat-SADPCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N1.65.2vmwareVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-22T06:01:05.499Z: Reported to Red Hat.
- 2026-04-22T05:08:41.318Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://spring.io/security/cve-2026-22747CVE reference, vmware
- https://access.redhat.com/security/cve/CVE-2026-22747CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2460487CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-22747.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Validation of Certificate with Host Mismatch
Improper Validation of Certificate with Host Mismatch represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.