Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-whpp-xv3h-rwxf

Spring Web Services: SSRF via unvalidated WS-Addressing reply destinations

CVSS 8.6 HighEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 11 Jun 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.ws:spring-ws-coreMaven>=5.0.0, <5.0.2 || >=4.1.0, <4.1.4 || >=4.0.0, <=4.0.18 || >=3.1.0, <=3.1.85.0.2, 4.1.4
Identifiers
GHSA-whpp-xv3h-rwxf · CVE-2026-40999
Weakness (CWE)
CWE-918
Tags
Published
11 Jun 2026
Updated
21 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring Web Services (org.springframework.ws:spring-ws-core) versions 5.0.0 through 5.0.1, 4.1.0 through 4.1.3, 4.0.0 through 4.0.18, and 3.1.0 through 3.1.8 are affected. When WS-Addressing uses non-anonymous ReplyTo or FaultTo addresses, Spring WS can open outbound connections to destinations taken from request headers without checking them, allowing server-side request forgery. Upgrade to spring-ws-core 5.0.2 or 4.1.4, or to a later release in your line; the source does not list a workaround for versions 4.0.x or 3.1.x.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.