CVE-2026-22748
MEDIUMCVE-2026-22748 is a medium-severity (CVSS 5.3) vulnerability in org.springframework.security:spring-security-oauth2-jose. O3 Security confirms whether CVE-2026-22748 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Potential Security Misconfiguration when Using withIssuerLocation
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.springframework.security:spring-security-oauth2-jose☕org.springframework.security:spring-security-oauth2-jose☕org.springframework.security:spring-security-oauth2-jose☕org.springframework.security:spring-security-oauth2-joseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-oauth2-jose | ≥ 6.3.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-oauth2-jose | ≥ 6.4.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-oauth2-jose | ≥ 6.5.0&&< 6.5.10 | 6.5.10 |
| ☕Maven | org.springframework.security:spring-security-oauth2-jose | ≥ 7.0.0&&< 7.0.5 | 7.0.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-oauth2-jose. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of org.springframework.security:spring-security-oauth2-jose has shipped for CVE-2026-22748 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-22748 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-22748. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-22748 in your dependencies?
O3 detects CVE-2026-22748 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.