How severe is CVE-2023-20883?

CVE-2023-20883 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-20883?

CVE-2023-20883 affects the following packages: org.springframework.boot:spring-boot-autoconfigure (Maven), org.springframework.boot:spring-boot-autoconfigure (Maven), org.springframework.boot:spring-boot-autoconfigure (Maven), org.springframework.boot:spring-boot-autoconfigure (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-20883?

Update org.springframework.boot:spring-boot-autoconfigure to 3.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-20883 is resolved across your whole dependency graph.

How do I detect CVE-2023-20883 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-autoconfigure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-20883 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2023-20883 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-20883 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-20883?

CVE-2023-20883 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-20883?

CVE-2023-20883 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-20883 published, and has it been updated?

CVE-2023-20883 was published on May 26, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-20883 — spring-boot-autoconfigure

HIGHFix: spring-projects/spring-boot@418dd1b

CVE-2023-20883 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.springframework.boot:spring-boot-autoconfigure. A fix is available for org.springframework.boot:spring-boot-autoconfigure — see the affected versions and patch details below.

Spring Boot Welcome Page Denial of Service

Also known asGHSA-xf96-w227-r7c4

Published

May 26, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-20883.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigure

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Specifically, an application is vulnerable if all of the conditions are true:

The application has Spring MVC auto-configuration enabled. This is the case by default if Spring MVC is on the classpath.
The application makes use of Spring Boot's welcome page support, either static or templated.
Your application is deployed behind a proxy which caches 404 responses.

Your application is NOT vulnerable if any of the following are true:

Spring MVC auto-configuration is disabled. This is true if WebMvcAutoConfiguration is explicitly excluded, if Spring MVC is not on the classpath, or if spring.main.web-application-type is set to a value other than SERVLET.
The application does not use Spring Boot's welcome page support.
You do not have a proxy which caches 404 responses.

Affected Spring Products and Versions

Spring Boot

3.0.0 to 3.0.6 2.7.0 to 2.7.11 2.6.0 to 2.6.14 2.5.0 to 2.5.14

Older, unsupported versions are also affected Mitigation

Users of affected versions should apply the following mitigations:

3.0.x users should upgrade to 3.0.7+
2.7.x users should upgrade to 2.7.12+
2.6.x users should upgrade to 2.6.15+
2.5.x users should upgrade to 2.5.15+

Users of older, unsupported versions should upgrade to 3.0.7+ or 2.7.12+.

Workarounds: configure the reverse proxy not to cache 404 responses and/or not to cache responses to requests to the root (/) of the application.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	≥ 3.0.0&&< 3.0.7	3.0.7`org.springframework.boot:spring-boot-autoconfigure:3.0.7`
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	≥ 2.7.0&&< 2.7.12	2.7.12`org.springframework.boot:spring-boot-autoconfigure:2.7.12`
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	≥ 2.6.0&&< 2.6.15	2.6.15`org.springframework.boot:spring-boot-autoconfigure:2.6.15`
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	all versions	2.5.15`org.springframework.boot:spring-boot-autoconfigure:2.5.15`

Affected Products

1 product · 4 configurations

Application

spring bootvmware

≥ 3.0.0 && ≤ 3.0.6

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-autoconfigure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.boot:spring-boot-autoconfigure to 3.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-20883 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat build of OptaPlanner 8	`spring-boot`	RHSA-2023:4200
Red Hat Fuse 7.12	`spring-boot`	RHSA-2023:3954
RHINT Camel-Springboot 3.18.3.P2	`spring-boot`	RHSA-2023:3641
RHINT Camel-Springboot 3.20.1.P1	`spring-boot`	RHSA-2023:3740
RHPAM 7.13.4 async	`spring-boot`	RHSA-2023:4983

Frequently Asked Questions

In Spring Boot versions 3.0.0 - 3.0.6, 2.7.0 - 2.7.11, 2.6.0 - 2.6.14, 2.5.0 - 2.5.14 and older unsupported versions, there is potential for a denial-of-service (DoS) attack if Spring MVC is used together with a reverse proxy cache. Specifically, an application is vulnerable if all of the conditions are true: * The application has Spring MVC auto-configuration enabled. This is the case by default if Spring MVC is on the classpath. * The application makes use of Spring Boot's welcome page support, either static or templated. * Your application is deployed behind a proxy which caches 404 respo