CVE-2026-40981
Telemetry drift only. No threshold crossed and no authority ruling changed.
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
When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the config server potentially exposing secrets from unintended GCP projects. 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-639: Authorization Bypass Through User-Controlled Key
- 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-2mh5-3cw6-hrrq
- severity
- 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- assigned by
- vmware
- published
- 2026-05-07
check us spring.io
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 7 May 2026 | 0.00011 | |
| 13 May 2026 | 0.00018 | |
| 8 Jun 2026 | 0.00021 | |
| 15 Jun 2026 | 0.0038 | scoring model v2026.06.15 |
| 30 Jun 2026 | 0.00435 | |
| 28 Sep 2026 | 0.00482 |
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.00 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-40981', '2026-10-30T23:59:59.999999Z', now());