How severe is GHSA-7m5c-fgwf-mwph?

GHSA-7m5c-fgwf-mwph has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7m5c-fgwf-mwph?

GHSA-7m5c-fgwf-mwph affects the following packages: org.springframework.hateoas:spring-hateoas (Maven), org.springframework.hateoas:spring-hateoas (Maven), org.springframework.hateoas:spring-hateoas (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7m5c-fgwf-mwph?

Update org.springframework.hateoas:spring-hateoas to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m5c-fgwf-mwph is resolved across your whole dependency graph.

How do I detect GHSA-7m5c-fgwf-mwph in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.hateoas:spring-hateoas. 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-7m5c-fgwf-mwph 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-7m5c-fgwf-mwph?

O3 pinpoints whether GHSA-7m5c-fgwf-mwph 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-7m5c-fgwf-mwph actively exploited in the wild?

No public exploit code has been indexed for GHSA-7m5c-fgwf-mwph 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-7m5c-fgwf-mwph?

GHSA-7m5c-fgwf-mwph has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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-7m5c-fgwf-mwph published, and has it been updated?

GHSA-7m5c-fgwf-mwph was published on July 17, 2023 and was last updated on February 16, 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-7m5c-fgwf-mwph: spring-hateoas (Medium 5.3)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk32th percentile-0.01%

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

3 pkgs affected

☕org.springframework.hateoas:spring-hateoas☕org.springframework.hateoas:spring-hateoas☕org.springframework.hateoas:spring-hateoas

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

Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server.

For the application to be affected, it needs to satisfy the following requirements:

It needs to use the reactive web stack (Spring WebFlux) and Spring HATEOAS to create links in hypermedia-based responses.
The application infrastructure does not guard against clients submitting (X-)Forwarded… headers.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.hateoas:spring-hateoas`	all versions	1.5.5
☕Maven	`org.springframework.hateoas:spring-hateoas`	≥ 2.0.0&&< 2.0.5	2.0.5
☕Maven	`org.springframework.hateoas:spring-hateoas`	≥ 2.1.0&&< 2.1.1	2.1.1

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.hateoas:spring-hateoas. 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.hateoas:spring-hateoas to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m5c-fgwf-mwph 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-7m5c-fgwf-mwph 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-7m5c-fgwf-mwph. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server. For the application to be affected, it needs to satisfy the following requirements: * It needs to use the reactive web stack (Spring WebFlux) and Spring HATEOAS to create links in hypermedia-based responses. * The

O3 Security · Impact-Aware SCA

Is GHSA-7m5c-fgwf-mwph in your dependencies?

O3 detects GHSA-7m5c-fgwf-mwph 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-7m5c-fgwf-mwph