← console
voxell vciy

CVE-2023-20873

ROUTINE

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

  1. Upgrade to the fixed version for your release line, or later: spring boot 2.5.15; spring boot 2.6.14; spring boot 2.7.11; spring boot 3.0.6 upper bounds of the CVE record's affected ranges
  2. 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
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

In Spring Boot versions 3.0.0 - 3.0.5, 2.7.0 - 2.7.10, and older unsupported versions, an application that is deployed to Cloud Foundry could be susceptible to a security bypass. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.6+. 2.7.x users should upgrade to 2.7.11+. Users of older, unsupported versions should upgrade to 3.0.6+ or 2.7.11+.

weakness
Security Bypass with Spring Boot when deployed to Cloud Foundry
affected
n/a Spring Boot
published ranges
vmware spring boot < 2.5.15; vmware spring boot >= 2.6.0 < 2.6.14; vmware spring boot >= 2.7.0 < 2.7.11; vmware spring boot >= 3.0.0 < 3.0.6
first unaffected version, by branch
spring boot 2.5.15; spring boot 2.6.14; spring boot 2.7.11; spring boot 3.0.6
fixed by package (from OSV advisories)
org.springframework.boot:spring-boot-actuator-autoconfigure (Maven): 2.5.15; 2.6.15; 2.7.11; 3.0.6 GHSA-g5h3-w546-pj7f
assigned by
vmware
published
2023-04-20

check us spring.io security.netapp.com 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

dateEPSSevent
21 Apr 20230.00043
2 May 20230.00148
8 May 20230.00331
8 Jul 20230.00144
17 Mar 20250.00328scoring model v2025.03.14
14 Feb 20260.00357
23 Feb 20260.00402
21 Apr 20260.00446
15 Jun 20260.01122scoring model v2026.06.15

29 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.

Sign in to add the researched section

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-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: spring boot 2.5.15; spring boot 2.6.14; spring boot 2.7.11; spring boot 3.0.6. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

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-2023-20873', '2026-11-01T23:59:59.999999Z', now());