Spring Framework has Improperly Implemented Security Check for Standard

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2018-1275: 57.41% estimated exploitation activity in the next 30 days; percentile 99.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 CVE-2018-1270 in the 4.3.x branch of the Spring Framework.

Published by the source

17 Oct 2018, 20:28 UTC

Last modified by the source

31 Jan 2025, 19:35 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3rmv-2pg5-xvqj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-1275

Advisory: Spring Framework has Improperly Implemented Security Check for Standard
IDs: CVE-2018-1275, GHSA-3rmv-2pg5-xvqj
Record: https://patchnext.com/advisories/cve-2018-1275 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.springframework:spring-messaging 5.0.5.RELEASE, 4.3.16.RELEASE. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework:spring-messaging: affected < 4.3.16.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; fixed in 5.0.5.RELEASE, 4.3.16.RELEASE

## Suggested inspection (read-only)
- Maven org.springframework:spring-messaging: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework:spring-messaging.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3rmv-2pg5-xvqj (GitHub-reviewed advisory GHSA-3rmv-2pg5-xvqj lists affected ranges: Maven org.springframework:spring-messaging >=0 =5.0.0.RELEASE <5.0.5.RELEASE)

Commands are suggestions: review each one before running it.