How severe is GHSA-xf96-w227-r7c4?

GHSA-xf96-w227-r7c4 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xf96-w227-r7c4?

GHSA-xf96-w227-r7c4 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 GHSA-xf96-w227-r7c4?

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 GHSA-xf96-w227-r7c4 is resolved across your whole dependency graph.

How do I detect GHSA-xf96-w227-r7c4 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xf96-w227-r7c4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-xf96-w227-r7c4?

O3 pinpoints whether GHSA-xf96-w227-r7c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xf96-w227-r7c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xf96-w227-r7c4 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 GHSA-xf96-w227-r7c4?

GHSA-xf96-w227-r7c4 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 55th 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.

When was GHSA-xf96-w227-r7c4 published, and has it been updated?

GHSA-xf96-w227-r7c4 was published on May 26, 2023 and was last updated on February 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xf96-w227-r7c4: Spring Boot Welcome Page Denial of Service…

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk55th percentile+0.21%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

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 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
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	≥ 2.7.0&&< 2.7.12	2.7.12
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	≥ 2.6.0&&< 2.6.15	2.6.15
☕Maven	`org.springframework.boot:spring-boot-autoconfigure`	all versions	2.5.15

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-xf96-w227-r7c4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xf96-w227-r7c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xf96-w227-r7c4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

O3 Security · Impact-Aware SCA

Is GHSA-xf96-w227-r7c4 in your dependencies?

O3 detects GHSA-xf96-w227-r7c4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-xf96-w227-r7c4