CVE-2026-22748GHSA-CVC6-Q2CP-2XHW
Potential Security Misconfiguration when Using withIssuerLocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.5.10, 7.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Vulnerability in Spring Spring Security. When an application configures JWT decoding with NimbusJwtDecoder or NimbusReactiveJwtDecoder, it must configure an OAuth2TokenValidator<Jwt> separately, for example by calling setJwtValidator.This issue affects Spring Security: from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.9, from 7.0.0 through 7.0.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring Security
From 6.3.0 · through 6.3.14; From 6.4.0 · through 6.4.14; From 6.5.0 · through 6.5.9; From 7.0.0 · through 7.0.4
- org.springframework.security:spring-security-oauth2-joseMaven
From 6.3.0 · through 6.3.14
- org.springframework.security:spring-security-oauth2-joseMaven
From 6.4.0 · through 6.4.14
- org.springframework.security:spring-security-oauth2-joseMaven
From 6.5.0 · fixed in 6.5.10
- org.springframework.security:spring-security-oauth2-joseMaven
From 7.0.0 · fixed in 7.0.5