Authenticated cross-request data disclosure via shared writer state
Published Aug 15, 2026 · Updated Aug 15, 2026
Information disclosure in Apache Struts 7.2.1 allows remote authenticated users to receive another request's JSON response. In the SMD/JSON-RPC path, JSONUtil reuses an injected StrutsJSONWriter whose write() operation mutates shared serialization fields without per-request isolation. Exploitation requires an authenticated user, the JSON plugin, non-default SMD support, and overlapping requests; the json result type uses a separate writer and is unaffected.
Summary
What happened
Information disclosure in Apache Struts 7.2.1 allows remote authenticated users to receive another request's JSON response. In the SMD/JSON-RPC path, JSONUtil reuses an injected StrutsJSONWriter whose write() operation mutates shared serialization fields without per-request isolation. Exploitation requires an authenticated user, the JSON plugin, non-default SMD support, and overlapping requests; the json result type uses a separate writer and is unaffected.
The record
- CVE
- CVE-2026-73632
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Struts
- Classifications
- CWE-567, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=7.2.1
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