CVE-2026-40994
RCE risk from disabled BSP validation in WSS4J SecurityInterceptor.
Is CVE-2026-40994 being exploited?
Not confirmed. CVE-2026-40994 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-40994?
CVE-2026-40994 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-40994?
Yes. A fix has been recorded for CVE-2026-40994. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40994 affect?
CVE-2026-40994 affects Spring Web Services 5.0.0-5.0.1, Spring Web Services 4.1.0-4.1.3, Spring Web Services 4.0.0-4.0.18, Spring Web Services 3.1.0-3.1.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40994?
Upgrade to latest Spring Web Services; re-enable BSP validation.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows WS-Security messages that violate BSP, weakening checks and enabling possible remote code execution.
Patch when possible
- affected>= 5.0.0 and < 5.0.1.1
- affected>= 4.1.0 and < 4.1.3.1
- affected>= 4.0.0 and < 4.0.19
- affected>= 3.1.0 and < 3.1.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.