Vulnerability in org.springframework:spring-websocket (CVE-2026-41838)
Summary
Vulnerability in org.springframework:spring-websocket (CVE-2026-41838). Confidential information can be exposed externally.
Original description
The description as published by the source.
IDs for WebSocket sessions in the spring-websocket module are not cryptographically unpredictable, which may be possible to exploit in combination with inadequate authorization rules.
Affected versions:
Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41838 has been found in org.springframework:spring-websocket.
Confidential information can be exposed externally. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.springframework:spring-websocket CVE-2026-41838" on the vendor's site.
CVE-2026-41838 (org.springframework:spring-websocket) — CWE-330 / CVSS v3 4.8
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-330) exists in org.springframework:spring-websocket.
Check the vendor advisory for the affected versions of org.springframework:spring-websocket.
Severity: Medium (CVSS 4.8/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springframework:spring-websocket を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-41838 libspring-java
- Ubuntu UBUNTU-CVE-2026-41838 libspring-java
References
- advisory nvd.nist.gov
- package github.com
- web spring.io
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com