CVE-2026-47893

Spring Framework Request Headers Included in Exception Reasons in HandshakeWebsocketService

Published Aug 27, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
A Spring WebFlux application that supports WebSocket connections may expose indirectly sensitive user information by including request headers in an exception reason.
Spring Framework 7.0.0 - 7.0.8
Spring Framework 6.2.0 - 6.2.19
Spring Framework 6.1.0 - 6.1.28
Spring Framework 6.0.0 - 6.0.30
Spring Framework 5.3.0 - 5.3.49
Spring Framework 5.2.25.RELEASE and earlier

Analysis

AI-generated

Technical impact

A Spring WebFlux application that supports WebSocket connections may expose request headers in the exception reason when a handshake error occurs. This information disclosure flaw allows an attacker to learn values from headers such as authentication tokens or session identifiers through error messages or logs, representing a breach of confidentiality consistent with CWE‑209.

Affected Systems

Any deployment of Spring Framework versions 7.0.0‑7.0.8, 6.2.0‑6.2.19, 6.1.0‑6.1.28, 6.0.0‑6.0.30, 5.3.0‑5.3.49, and 5.2.25.RELEASE or earlier that uses Spring WebFlux with WebSocket support is vulnerable.

Risk and Exploitability

The CVSS score is 7.5 and the EPSS score is <1%, leaving the exploitation probability low. A user could trigger the flaw by sending a crafted WebSocket handshake request that causes an exception; this is the likely attack vector inferred from the description. The vulnerability is not cataloged in CISA KEV. If exploited, the attacker could obtain header data from error responses or application logs, potentially compromising authentication or session continuity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Framework to a patched release—7.0.9 or later, 6.2.20 or later, 6.1.29 or later, 6.0.31 or later, 5.3.50 or later, or 5.2.26 or later.
  • If an upgrade is not immediately possible, configure the application to suppress detailed exception messages so that request headers are omitted from client responses and logs, limiting the data an attacker can see.
  • Review any tokens or sensitive values that may have already been exposed through logs and rotate them.

Generated by OpenCVE AI on August 29, 2026 at 00:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Framework
CPEs cpe:2.3:a:vmware:spring_framework:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Framework
Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
Weaknesses CWE-209
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
First Time appeared Spring
Spring spring Framework
Vendors & Products Spring
Spring spring Framework
Type Values Removed Values Added
Description A Spring WebFlux application that supports WebSocket connections may expose indirectly sensitive user information by including request headers in an exception reason. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.25.RELEASE and earlier
Title Spring Framework Request Headers Included in Exception Reasons in HandshakeWebsocketService
References
Weaknesses
  • CWE-209

    Generation of Error Message Containing Sensitive Information

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 7:12 PM
Reserved
May 20, 2026, 10:01 AM
Status
Analyzed
Published
Aug 27, 2026, 6:17 AM
Modified
Sep 1, 2026, 8:38 PM