Skip to content
VulniPulse
Advisory severityHigh7.5Apache Software Foundation

High [CVE-2026-73635] Allocation of resources without limits or throttling vulnerability in Apache Struts

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

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-73635 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationStruts
Open source 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

Allocation of resources without limits or throttling vulnerability in Apache Struts.

When no fixed locale is configured, the locale used for localized-text lookups is taken from the incoming request, allowing an unauthenticated remote client to cause the framework's internal localized-text caches to grow without bound and exhaust the Java heap, denying service to other users. Applications that configure a fixed locale are not affected.

This issue affects Apache Struts: from 2.0.0 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.0.0 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 months ago·verify at source

Fixed versions
  • 6.11.0
  • 7.3.0

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

Mitigation checklist

Recommended fix / mitigation
  • Applications that configure a fixed locale are not affected.
  • 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 months 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.