Request smuggling via mishandled TRACE requests
Published Jul 28, 2026 · Updated Jul 28, 2026
HTTP request smuggling in IBM WebSphere 8.5 and 9.0 and Liberty 17.0.0.3 through 26.0.0.8 allows remote attackers to inject requests. The HTTP channel improperly handles TRACE requests, creating a parsing discrepancy that lets a second request pass an intermediary. The issue is unauthenticated and network-reachable only when a listed servlet feature is enabled, and successful exploitation can bypass access controls and expose or alter application data.
Summary
What happened
HTTP request smuggling in IBM WebSphere 8.5 and 9.0 and Liberty 17.0.0.3 through 26.0.0.8 allows remote attackers to inject requests. The HTTP channel improperly handles TRACE requests, creating a parsing discrepancy that lets a second request pass an intermediary. The issue is unauthenticated and network-reachable only when a listed servlet feature is enabled, and successful exploitation can bypass access controls and expose or alter application data.
The record
- CVE
- CVE-2026-15325
- Published
- Jul 28, 2026
- Updated
- Jul 28, 2026
- Vendor
- OpenBMC Project
- Product
- IBM WebSphere Application Server Liberty
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2026CVE publishedPublication date reported by the CVE source.
- Jul 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.0.0.3 <=26.0.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo