How severe is GHSA-gx3f-hq7p-8fxv?

GHSA-gx3f-hq7p-8fxv has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

How do I fix GHSA-gx3f-hq7p-8fxv?

Update org.springframework.cloud:spring-cloud-netflix-hystrix-dashboard to 2.2.10.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gx3f-hq7p-8fxv is resolved across your whole dependency graph.

How do I detect GHSA-gx3f-hq7p-8fxv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-netflix-hystrix-dashboard. 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-gx3f-hq7p-8fxv 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-gx3f-hq7p-8fxv?

O3 pinpoints whether GHSA-gx3f-hq7p-8fxv 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-gx3f-hq7p-8fxv actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-gx3f-hq7p-8fxv, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-gx3f-hq7p-8fxv?

GHSA-gx3f-hq7p-8fxv has an EPSS (Exploit Prediction Scoring System) score of 12.7%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-gx3f-hq7p-8fxv?

GHSA-gx3f-hq7p-8fxv is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-gx3f-hq7p-8fxv?

A Nuclei detection template exists for GHSA-gx3f-hq7p-8fxv, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-gx3f-hq7p-8fxv published, and has it been updated?

GHSA-gx3f-hq7p-8fxv was published on November 23, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-gx3f-hq7p-8fxv

HIGH

Code injection in spring-cloud-netflix-hystrix-dashboard

Also known asCVE-2021-22053

Published

Nov 23, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

12.7%probability of exploitation in next 30 days

Moderate Risk96th percentile-76.87%

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

1 pkg affected

☕org.springframework.cloud:spring-cloud-netflix-hystrix-dashboard

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

Applications using the spring-cloud-netflix-hystrix-dashboard expose a way to execute code submitted within the request URI path during the resolution of view templates. When a request is made at /hystrix/monitor;[user-provided data], the path elements following hystrix/monitor are being evaluated as SpringEL expressions, which can lead to code execution.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.cloud:spring-cloud-netflix-hystrix-dashboard`	all versions	2.2.10.RELEASE

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Applications using both `spring-cloud-netflix-hystrix-dashboard` and `sp…

github.comGithubNov 2021

Applications using both `spring-cloud-netflix-hystrix-dashboard` and `sp…

unit42.paloaltonetworks.comAPIMay 2022

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.cloud:spring-cloud-netflix-hystrix-dashboard. 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.cloud:spring-cloud-netflix-hystrix-dashboard to 2.2.10.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gx3f-hq7p-8fxv 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-gx3f-hq7p-8fxv 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-gx3f-hq7p-8fxv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Applications using the `spring-cloud-netflix-hystrix-dashboard` expose a way to execute code submitted within the request URI path during the resolution of view templates. When a request is made at `/hystrix/monitor;[user-provided data]`, the path elements following `hystrix/monitor` are being evaluated as SpringEL expressions, which can lead to code execution.

O3 Security · Impact-Aware SCA

Is GHSA-gx3f-hq7p-8fxv in your dependencies?

O3 detects GHSA-gx3f-hq7p-8fxv 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