CVE-2026-41854: Spring Framework · Server-Side Request Forgery (SSRF)
Affects Spring FrameworkSource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium : upgrade to 7.0.7.1 or 6.2.18.1 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.0.7.1, 6.2.18.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jun 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
Upgrade Spring Framework to 7.0.7.1 or 6.2.18.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SpringSpring Framework | Affected
| Fixed in
|
| SpringSpring Framework | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should exercise caution when using UriComponentsBuilder to parse and validate externally supplied URLs. Consider implementing additional validation or filtering of URLs before processing.
Description
Due to incorrect host parsing, applications that rely on UriComponentsBuilder to parse and validate an externally provided URL string may be exposed to a server-side request forgery (SSRF) attack. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18.