Skip to main content
VulnerabilityPublished Updated

CVE-2026-41694: Spring Security · Improper Verification of Cryptographic Signature

Affects Spring SecuritySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low · fixed in 7.0.5.1 : update Spring Security when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.0.5.1, 6.5.10.2, 6.4.17 +3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SpringSpring SecurityAffected
  • >=7.0.0 <7.0.5.1
Fixed in
  • 7.0.5.1
SpringSpring SecurityAffected
  • >=6.5.0 <6.5.10.2
Fixed in
  • 6.5.10.2
SpringSpring SecurityAffected
  • >=6.4.0 <6.4.17
Fixed in
  • 6.4.17
SpringSpring SecurityAffected
  • >=6.3.0 <6.3.17
Fixed in
  • 6.3.17
SpringSpring SecurityAffected
  • >=5.8.0 <5.8.26
Fixed in
  • 5.8.26
SpringSpring SecurityAffected
  • >=5.7.0 <5.7.24
Fixed in
  • 5.7.24

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider restricting or closely monitoring SAML traffic and usage to mitigate potential exploitation.

Description

Since Spring Security SAML decrypts SAML Responses as well as elements of SAML LogoutRequests and LogoutResponses without requiring a valid signature, attackers may be able to craft these SAML payloads and use the Service Provider as a decryption oracle. Affected versions: Spring Security 5.7.0 through 5.7.23; 5.8.0 through 5.8.25; 6.3.0 through 6.3.16; 6.4.0 through 6.4.16; 6.5.0 through 6.5.10; 7.0.0 through 7.0.5.

References

Community reviews

Loading reviews…