Spring SecurityFramework / library · VMware
CVE-2026-22748
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWhen configuring JWT decoding with NimbusJwtDecoder or NimbusReactiveJwtDecoder in Spring Security, an OAuth2TokenValidator<Jwt> must be explicitly configured via setJwtValidator(). Without this validator, JWTs may not be properly validated for signature, expiration, issuer, or other claims, potentially allowing invalid or malicious tokens to be accepted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring SecurityFramework / library
< 6.3.15>= 6.4.0, < 6.4.15>= 6.5.0, < 6.5.10>= 7.0.0, < 7.0.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Spring Security versionInspect your project dependencies (pom.xml, build.gradle, gradle.lock, or Maven dependency:tree) to find the spring-security-version or spring-security-core version.Affected if The version is < 6.3.15, OR >= 6.4.0 and < 6.4.15, OR >= 6.5.0 and < 6.5.10, OR >= 7.0.0 and < 7.0.5.
-
Identify JWT decoder usageSearch your codebase for imports or usage of com.nimbusds.jwt.proc.NimbusJwtDecoder or org.springframework.security.oauth2.jwt.reactive.NimbusReactiveJwtDecoder.Affected if Either NimbusJwtDecoder or NimbusReactiveJwtDecoder is used in your application code or configuration.
-
Verify JWT validator is configuredSearch for code that initializes NimbusJwtDecoder or NimbusReactiveJwtDecoder and check whether setJwtValidator() is called with an OAuth2TokenValidator<Jwt> instance (such as JwtTimestampValidator, JwtIssuerValidator, or a custom OAuth2TokenValidator).Affected if The decoder is initialized WITHOUT calling setJwtValidator() with a non-null OAuth2TokenValidator.
You are affected if your Spring Security version falls within the affected ranges AND you use NimbusJwtDecoder or NimbusReactiveJwtDecoder without explicitly configuring an OAuth2TokenValidator via setJwtValidator().
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.3.156.4.156.5.10
Configure an OAuth2TokenValidator<Jwt> (such as a JwtTimestampValidator or custom validator) using setJwtValidator() when initializing NimbusJwtDecoder or NimbusReactiveJwtDecoder to ensure proper JWT validation before trusting token claims.
6.3.15 (for 6.3.x) | 6.4.15 (for 6.4.x) | 6.5.10 (for 6.5.x) | 7.0.5 (for 7.0.x)
- 1. Identify your current Spring Security version from your project dependencies (e.g., pom.xml or build.gradle)
- 2. Determine which version branch you are on (6.3.x, 6.4.x, 6.5.x, or 7.0.x)
- 3. Upgrade to the corresponding fixed version: 6.3.15, 6.4.15, 6.5.10, or 7.0.5
- 4. Verify that your application compiles and tests pass after the upgrade
- 5. If using NimbusJwtDecoder or NimbusReactiveJwtDecoder, ensure you explicitly configure an OAuth2TokenValidator<Jwt> using setJwtValidator() method to validate JWT tokens properly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22748 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data