Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.1%top 77%

CVE-2026-22748: Vulnerability in Spring Spring Security

0
Medium
VulnerabilityCVE-2026-22748cvecve-2026-22748
Published: Wed Apr 22 2026 (04/22/2026, 05:15:03 UTC)
Source: CVE Database V5
Vendor/Project: Spring
Product: Spring Security

Description

CVE-2026-22748 is a medium severity vulnerability in Spring Security affecting versions 6. 3. 0 through 6. 3. 14, 6. 4. 0 through 6. 4. 14, 6. 5.

CVSS v3.1

Score 5.3medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/29/2026, 11:16:02 UTC

Technical Analysis

The vulnerability in Spring Security concerns the configuration of JWT decoding with NimbusJwtDecoder or NimbusReactiveJwtDecoder. Applications must explicitly configure an OAuth2TokenValidator<Jwt> to ensure proper validation of JWT tokens. Failure to do so may result in acceptance of invalid or malicious tokens. This affects multiple Spring Security versions from 6.3.0 up to 7.0.4. The CVSS 3.1 base score is 5.3 (medium severity), reflecting network attack vector, high attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. No patch or official remediation level has been provided as of the published date.

Potential Impact

The vulnerability can lead to improper validation of JWT tokens, potentially allowing attackers to bypass intended security controls related to token integrity and authorization. This impacts the integrity of the application but does not affect confidentiality or availability. No known exploits are reported in the wild at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, ensure that applications explicitly configure an OAuth2TokenValidator<Jwt> when using NimbusJwtDecoder or NimbusReactiveJwtDecoder to enforce proper JWT validation. Review application configurations to verify that setJwtValidator or equivalent validation mechanisms are properly implemented.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
vmware
Date Reserved
2026-01-09T06:55:03.990Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69e8609e19fe3cd2cd71451a

Added to database: 4/22/2026, 5:46:06 AM

Last enriched: 4/29/2026, 11:16:02 AM

Last updated: 6/8/2026, 3:56:13 AM

Views: 794

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses