# CVE-2026-47893: Spring Framework information disclosure in WebSocket exception handling

Source: https://junglewise.ai/threats/cve-2026-47893-spring-framework-information-disclosure-in-websocket-exception  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-27. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-47893 · Severity: high · CVSS 7.5 · Published 2026-08-27

Spring Framework applications using WebSocket connections may leak sensitive request headers in error messages. When a WebSocket connection fails, the framework inadvertently includes HTTP headers (which may contain authentication tokens, session IDs, or other credentials) in exception details visible to end users. This could allow an attacker to harvest sensitive information from error responses.

Technologies: [VMware Spring Framework](https://junglewise.ai/threats/technologies/spring-framework). Vendors: [VMware](https://junglewise.ai/threats/vendors/vmware).

## Quick answers

**Is CVE-2026-47893 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-47893 being exploited in the wild.

**How severe is CVE-2026-47893?** High severity, with a CVSS score of 7.5, published 27 August 2026.

**Which products and versions are affected?** VMware Spring Framework 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, 5.2.25.RELEASE and earlier.

**Is there a fix for CVE-2026-47893?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-47893 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-47893?** Check whether you run VMware Spring Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an information disclosure flaw in Spring WebFlux's WebSocket handling. When WebSocket connections encounter errors, the framework includes raw HTTP request headers in the exception reason string. The vulnerable component is the WebSocket protocol handler, which does not sanitize headers before exposing them in error messages. Attack vector is network-based; an attacker can trigger a WebSocket connection error and observe the exception response to extract headers. No authentication is required. The impact allows retrieval of potentially sensitive headers such as Authorization, Cookie, or custom authentication tokens. Patches are available for all affected versions.

## Affected products

- VMware Spring Framework 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, 5.2.25.RELEASE and earlier

## Timeline

- 2026-08-27: disclosed

## References

- [https://spring.io/security/cve-2026-47893](https://spring.io/security/cve-2026-47893)

## Related threats

- [Spring Framework stream corruption in Server-Sent Events](https://junglewise.ai/threats/cve-2026-59313-spring-framework-stream-corruption-in-server-sent-events)
- [Spring Framework XML maxInMemorySize enforcement bypass](https://junglewise.ai/threats/cve-2026-47891-spring-framework-xml-maxinmemorysize-enforcement-bypass)
- [Spring Framework UrlHandlerFilter open redirect vulnerability](https://junglewise.ai/threats/cve-2026-47883-spring-framework-urlhandlerfilter-open-redirect-vulnerability)
- [VMware Spring Framework denial of service in static resource resolution](https://junglewise.ai/threats/cve-2026-41842-vmware-spring-framework-dos-in-static-resource-resolution)
- [VMware Spring Framework deserialization in JMS message converters](https://junglewise.ai/threats/cve-2026-41855-vmware-spring-framework-deserialization-in-jms-message-converters)
