CVE-2026-22748: Spring Security has Potential Security Misconfiguration when Using withIssuerLocation

CVE-2026-22748 · Severity: medium · CVSS 5.3 · Published 2026-04-22

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.

Technologies: VMware Spring Security. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-22748 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-22748 being exploited in the wild.
How severe is CVE-2026-22748?
Medium severity, with a CVSS score of 5.3, published 22 April 2026.
Which products and versions are affected?
org.springframework.security:spring-security-oauth2-jose (Maven) ECOSYSTEM:introduced=6.3.0,last_affected=6.3.14.
Is there a fix for CVE-2026-22748?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-22748?
Check whether you run org.springframework.security:spring-security-oauth2-jose (Maven) or VMware Spring Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • org.springframework.security:spring-security-oauth2-jose (Maven) ECOSYSTEM:introduced=6.3.0,last_affected=6.3.14
  • VMware Spring Security

Identifiers

  • CVE-2026-22748
  • GHSA-cvc6-q2cp-2xhw

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.