CVE-2026-22746: Spring Security · Timing Side Channel
Affects Spring SecuritySource CVE Database V5
Not known to be exploited · CVSS 3.7 Low.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SpringSpring Security | Affected
| Fixed in– |
Mavenorg.springframework.security/spring-security-corepkg:maven/org.springframework.security/spring-security-coreOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, review application use of UserDetails attributes for user state management and consider additional protective measures against timing attacks. Avoid relying solely on these attributes for critical access control decisions. Monitor official Spring Security advisories for updates and patches.
Description
CVE-2026-22746 is a low severity vulnerability in Spring Security affecting versions from 5.7.0 through 5.7.22, 5.8.0 through 5.8.24, 6.3.