NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2017-8045 — spring-amqp

CRITICAL

CVE-2017-8045 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data 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.

Deserialization of Untrusted Data in Spring AMQP

Also known asGHSA-vqqg-xgv7-cf68
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk
2.33%2.90%3.48%4.05%2.8%3.6%May 26Sep 26Nov 26

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

3 pkgs affected
☕org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp

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 Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.amqp:spring-amqpall versions1.5.7org.springframework.amqp:spring-amqp:1.5.7
☕Mavenorg.springframework.amqp:spring-amqp≥ 1.6.0&&< 1.6.111.6.11org.springframework.amqp:spring-amqp:1.6.11
☕Mavenorg.springframework.amqp:spring-amqp≥ 1.7.0&&< 1.7.41.7.4org.springframework.amqp:spring-amqp:1.7.4

Affected Products

1 product · 27 configurations
Application
spring advanced message queuing protocolpivotal_software
22 versions
1.5.01.5.11.5.21.5.31.5.41.5.51.5.61.6.01.6.11.6.21.6.31.6.4

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update org.springframework.amqp:spring-amqp to 1.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8045 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack.
O3 Security · Impact-Aware SCA

Is CVE-2017-8045 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-8045: spring-amqp RCE — Fixed in 1.5.7