How to Fix CVE-2026-22747: Spring Security (Bundle Sibling)
By Sai Kiran Pandrala
Last verified: 2026-05-25
CVE-2026-22747 is a sibling vulnerability in the same vendor advisory as CVE-2026-22746. Applying the patched build named in the primary write-up closes this CVE as well.
| Severity | CVSS 6.8 - Medium |
|---|---|
| Actively exploited? | Not currently in CISA KEV |
| Affected | Same as the bundle - see CVE-2026-22746 |
| Fixed in | Same patched build as CVE-2026-22746 (See vendor advisory) |
| Type (CWE) | Not verified |
What's different about CVE-2026-22747?
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.
The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.
How to fix CVE-2026-22747
Apply the patched build per the primary write-up: How to Fix CVE-2026-22746.
The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.
Frequently asked questions
Is CVE-2026-22747 fixed by the same patch as CVE-2026-22746?
Yes. CVE-2026-22747 ships in the same vendor advisory as CVE-2026-22746. Applying the patched build named in the primary write-up closes both.
What is the CVSS score for CVE-2026-22747?
The CVSS base score is 6.8 (Medium).
Is it being exploited?
It is not currently listed in CISA KEV.
References
- Official vendor advisory: https://spring.io/security/cve-2026-22747
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-22747
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-22746
*Part of the Spring Security bundle. Full procedure at CVE-2026-22746.*