GHSA-w4g2-9hj6-5472 — spring-amqp
MEDIUMGHSA-w4g2-9hj6-5472 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in org.springframework.amqp:spring-amqp. A fix is available for org.springframework.amqp:spring-amqp — see the affected versions and patch details below.
Moderate severity vulnerability that affects com.rabbitmq:amqp-client and org.springframework.amqp:spring-amqp
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-w4g2-9hj6-5472 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp☕com.rabbitmq:amqp-client☕com.rabbitmq:amqp-clientReal-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
Pivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 2.0.0&&< 2.0.6 | 2.0.6org.springframework.amqp:spring-amqp:2.0.6 |
| ☕Maven | org.springframework.amqp:spring-amqp | all versions | 1.7.10org.springframework.amqp:spring-amqp:1.7.10 |
| ☕Maven | com.rabbitmq:amqp-client | all versions | 4.8.0com.rabbitmq:amqp-client:4.8.0 |
| ☕Maven | com.rabbitmq:amqp-client | ≥ 5.0.0&&< 5.4.0 | 5.4.0com.rabbitmq:amqp-client:5.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.amqp:spring-amqp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.amqp:spring-amqp to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4g2-9hj6-5472 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w4g2-9hj6-5472 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-w4g2-9hj6-5472. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w4g2-9hj6-5472 in your dependencies?
O3 Security finds GHSA-w4g2-9hj6-5472 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.