CVE-2026-22748Network attack vector

Authenticated token acceptance via omitted issuer validator

Published Apr 22, 2026 · Updated Apr 22, 2026

Improper issuer validation in Spring Security allows remote authenticated users to have JWTs from an unintended issuer accepted. The NimbusJwtDecoder.withIssuerLocation and NimbusReactiveJwtDecoder.withIssuerLocation builders discover issuer metadata but do not add an issuer validator by default, so signature-valid JWTs need not match the configured issuer. The flaw is reachable only when an application uses either builder without separately installing an OAuth2TokenValidator; acceptance is limited to claims and privileges granted by that application.

CVSS severity5.3
Medium
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper issuer validation in Spring Security allows remote authenticated users to have JWTs from an unintended issuer accepted. The NimbusJwtDecoder.withIssuerLocation and NimbusReactiveJwtDecoder.withIssuerLocation builders discover issuer metadata but do not add an issuer validator by default, so signature-valid JWTs need not match the configured issuer. The flaw is reachable only when an application uses either builder without separately installing an OAuth2TokenValidator; acceptance is limited to claims and privileges granted by that application.

The record

CVE
CVE-2026-22748
Published
Apr 22, 2026
Updated
Apr 22, 2026
Vendor
Spring
Product
Spring Security
Classifications
CWE-20, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 22, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 22, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.3.0 <=6.3.14
  2. Affected versionversion=6.4.0 <=6.4.14
  3. Affected versionversion=6.5.0 <=6.5.9
  4. Affected versionversion=7.0.0 <=7.0.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Spring · Spring Securityversion=6.3.0 <=6.3.14; version=6.4.0 <=6.4.14; version=6.5.0 <=6.5.9; version=7.0.0 <=7.0.4

Published CVSS scores

5.3GitHubCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
6.5NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-20Improper Input Validation
T1078Valid Accounts

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo