CVE-2026-40999: Spring WS SSRF via unvalidated WS-Addressing reply destinations

Published Jun 11, 2026
·
Updated

When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to.

Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

Affected Software

5 affected components
Spring Spring Web Services>=5.0.0<=5.0.1, >=4.1.0<=4.1.3, >=4.0.0<=4.0.18, >=3.1.0<=3.1.8
Broadcom Spring Web Services<3.1.9
Broadcom Spring Web Services>=4.0.0<4.0.19
Broadcom Spring Web Services>=4.1.0<4.1.3.1
Broadcom Spring Web Services>=5.0.0<5.0.1.1

Event History

Jun 11, 2026
CVE Published
via MITRE·05:04 AM
Data Sourced
via MITRE·05:04 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-40999?

CVE-2026-40999 has a severity score of 8.6, categorizing it as high risk.

2

How do I fix CVE-2026-40999?

To fix CVE-2026-40999, ensure to validate WS-Addressing reply destinations to prevent unintended outbound connections.

3

What types of applications are affected by CVE-2026-40999?

CVE-2026-40999 affects applications using Spring Web Services with unvalidated WS-Addressing reply addresses.

4

What is the risk associated with CVE-2026-40999?

The risk associated with CVE-2026-40999 involves potential SSRF attacks that can lead to unauthorized access to internal services.

5

When was CVE-2026-40999 published?

CVE-2026-40999 was published on June 11, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203