CVE-2026-40982
Description revised (poc_count, poc_public, poc_url). The record changed; nothing in the observed threat did.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 3.1.14; 4.1.10; 4.2.7; 4.3.3; 5.0.3 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
- weakness
- CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- affected
- Spring Cloud Config
- published ranges
- vmware spring cloud config >= 3.1.0 < 3.1.14; vmware spring cloud config >= 4.1.0 < 4.1.10; vmware spring cloud config >= 4.2.0 < 4.2.7; vmware spring cloud config >= 4.3.0 < 4.3.3; and 1 more on the CVE page
- fixed in
- 3.1.14; 4.1.10; 4.2.7; 4.3.3; 5.0.3
- fixed by package (from OSV advisories)
- org.springframework.cloud:spring-cloud-config-server (Maven): 4.3.3; 5.0.3 GHSA-6g23-24mc-hx6x
- severity
- 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- assigned by
- vmware
- published
- 2026-05-07
check us spring.io
Exploit code held, dated
- exploit code
- 1 public proof-of-concept repository, first seen 2026-08-05 (PoC-in-GitHub).
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 7 May 2026 | 0.00112 | |
| 13 May 2026 | 0.00143 | |
| 8 Jun 2026 | 0.00168 | |
| 15 Jun 2026 | 0.00793 | scoring model v2026.06.15 |
| 30 Jun 2026 | 0.00727 | |
| 28 Sep 2026 | 0.00819 |
6 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 3.1.14; 4.1.10; 4.2.7; 4.3.3; 5.0.3. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-40982', '2026-10-31T23:59:59.999999Z', now());