CVE Intelligence
Skip to main content
Remote Code Exec

CVE-2026-73632

CVE-2026-73632 — Apache Struts: Shared serialization state in the JSON plugin

Exposure of data element to wrong session vulnerability in the JSON plugin of Apache Struts. Per-response serialization state could be shared across concurrent requests, allowing response content associated with one request to become observable in another. Only the SMD / JSON-RPC handling of the JSON interceptor is affected, which is not enabled by default; applications using the json result type are not affected. This issue affects Apache Struts: 7.2.1. Users are recommended to upgrade to version 7.3.0, which fixes the issue.

Published Updated Sources: NVD, Apache Software Foundation (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

Apache

Apache Struts

CVSS base

Unscored

no source published a base score

Remediation

The vendor's own words where we have them.

Upgrade Apache Struts to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
ApacheApache Struts7.2.1Vulnerable

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-567 · Unsynchronized Access to Shared Data in a Multithreaded Context

  • Read Application Data
  • Modify Application Data
  • DoS: Instability
  • DoS: Crash, Exit, or Restart

Mitigation: Remove the use of static variables used between servlets. If this cannot be avoided, use synchronized access for these variables.::

Weakness & attack patterns

  • CWE-567

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-25 · Forced Deadlock
  • T1499.004Endpoint Denial of Service: Application or System Exploitation

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

EDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Initial · CVE published

    Aug 15, 2026 · NVD

  3. Added · GHSA-87hf-473v-8h9c published (unknown)

    Aug 15, 2026 · GitHub Security Advisory

Source activity

Readings a source repeats on a schedule, counted rather than listed.

  • CVE modified by NIST, Modified, LinkAug 15, 2026 · SOCRadar CTI

References

3 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-73632 is Apache Struts: Shared serialization state in the JSON plugin, a unscored vulnerability affecting Apache Struts from Apache Software Foundation. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-73632. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-73632. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.