maven package report

Is org.springframework:spring-messaging safe?

3 known vulnerabilities, worst severity CRITICAL.

cvss
9.0

how bad it is if exploited, out of 10

epss
57.4%

chance of exploitation in the next 30 days

xyz score
5.9

CyberXYZ composite, out of 10

fig. 01 — GHSA-3rmv-2pg5-xvqj, the advisory selected below

// advisories

GHSA-3rmv-2pg5-xvqj

CRITICALCVE-2018-1275

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE addresses the partial fix for C

Affected
>= 5.0.0.RELEASE, < 5.0.5.RELEASE, < 4.3.16.RELEASE
Fixed in
5.0.5.RELEASE
Weakness
CWE-94
Published
2018-10-17
Source
github

GHSANVDMITREreferencereferencereferencereferencereferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 03:28 UTC. The most recent advisory here was published 2022-05-13. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is org.springframework:spring-messaging safe? maven package security report | CyberXYZ