Skip to content
VulniPulse
High7.5Apache Software Foundation Updated

High [CVE-2026-73633] Uncontrolled resource consumption vulnerability in the JSON plugin of Apache Struts

This high-severity Apache Software Foundation advisory covers CVE-2026-73633 affecting Apache Struts.

CVE-2026-73633 Published Aug 14, 2026Updated by vendor Aug 14, 2026
Affected products & platforms
Apache Software FoundationStruts
Open vendor advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Uncontrolled resource consumption vulnerability in the JSON plugin of Apache Struts. When an application is configured to populate actions from a JSON request body, the plugin reads that body into memory without bounding how much it will accept, so a single request can exhaust the heap and deny service to other users.

The plugin's configurable JSON input length limit does not bound this read. The JSON plugin is an optional component; applications that do not use it, or use it without enabling JSON request-body handling, are not affected.

This issue affects Apache Struts: from 2.1.8 through 2.3.37, from 2.5.0 through 2.5.33, from 6.0.0 through 6.10.0, from 7.0.0 through 7.2.1.

Users are recommended to upgrade to version 6.11.0 or 7.3.0, which fixes the issue.

Affected versions
  • 2.1.8 through 2.3.37
  • 2.5.0 through 2.5.33
  • 6.0.0 through 6.10.0
  • 7.0.0 through 7.2.1.
  • through 7.2.1

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions
  • 6.11.0
  • 7.3.0

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • The plugin's configurable JSON input length limit does not bound this read.
  • Users are recommended to upgrade to version 6.11.0 or 7.3.0, which fixes the issue.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.