CyberSecBulletin
CVE-2026-22747NVD status: Modified

Spring Security: Improper Validation of Certificate with Host Mismatch

CVE-2026-22747 is a high-severity improper validation of certificate with host mismatch vulnerability in Spring Security from Spring, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Spring Security versions: 7.0.0 through 7.0.4. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Spring Security you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on spring.io for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
SpringSpring Security7.0.0 through 7.0.4Not stated
Red HatOpenShift Developer Tools and ServicesNot specified in the recordNot stated
Red HatRed Hat build of Apache Camel for Spring Boot 4Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel - HawtIO 4Not specified in the recordNot stated
Red HatRed Hat build of QuarkusNot specified in the recordNot stated
Red HatRed Hat Data Grid 8Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat OpenShift Dev SpacesNot specified in the recordNot stated
Red HatRed Hat Process Automation 7Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.8MediumCNA (vmware.com)
CVSS 3.18.1HighNVD
CVSS 3.18.1HighCNA

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Validation of Certificate with Host Mismatch

The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.

How developers prevent this class of flaw

  • In order to ensure data integrity, the certificate must be valid, and it must pertain to the site that is being accessed.Fully check the hostname of the certificate and provide the user with adequate information about the nature of the problem and how to proceed.
  • If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
  • Be careful of other weaknesses in the code that checks the hostname, since it is still possible to incorrectly check the hostname. For example, attackers could create a certificate with a name that begins with a trusted name followed by a NUL byte, which could cause some string-based comparisons to only examine the portion that contains the trusted name.

More Improper Validation of Certificate with Host Mismatch vulnerabilities (CWE-297)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Spring Security

All Spring Security vulnerabilities

Recent Improper Validation of Certificate with Host Mismatch vulnerabilities

Spotted an error? Tell us.