Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-40997: Several Spring WS integration paths with Spring Security could surface detailed account state (for example loc

31
Routine
MEDIUM 5.3REMOTEUPGRADE

CVE-2026-40997 is a medium-severity flaw (CVSS 5.3) affecting spring web services. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state. Affected versions: Spring Web Services 5.0.0 through 5.0.1;

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 70%)
CISA exploited listNo
WeaknessCWE-209
Published2026-06-11
Last modified2026-09-04
Publisher (CNA): VMware · Vendor: broadcom

Share: LinkedIn · X · Reddit

Last updated 2026-09-04 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

broadcom spring web services UPGRADE
Affected: < 3.1.9 · >= 4.0.0 and < 4.0.19 · >= 4.1.0 and < 4.1.3.1 · >= 5.0.0 and < 5.0.1.1
Fixed in: 3.1.9, 4.0.19, 4.1.3.1, 5.0.1.1
Safe to downgrade to: a release before 4.0.0
1. Check installed version
apt-cache policy spring-web-services || rpm -q spring-web-services || spring-web-services --version
2. UPGRADE to 3.1.9 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-web-services
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-web-services
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)
apt-cache madison spring-web-services sudo apt install spring-web-services=<VERSION_BEFORE_4.0.0> sudo apt-mark hold spring-web-services
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-web-services sudo dnf downgrade spring-web-services-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add spring-web-services
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40997?

spring web services: upgrade to 3.1.9, 4.0.19, 4.1.3.1, 5.0.1.1. Exact commands for each OS are on this page.

Is CVE-2026-40997 being exploited?

CVE-2026-40997 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40997 affect?

CVE-2026-40997 affects spring web services. Severity is medium (CVSS 5.3). Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with ge

How urgent is CVE-2026-40997?

Priority 31/100. Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.