DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Summary
Unbounded read of a REST request bodyWho should read this | All Struts 2 developers and users of the REST plugin |
|---|---|
Impact of vulnerability | Denial of Service |
Maximum security rating | Important |
Recommendation | Upgrade to Struts 7.4.0 at least, or to Struts 6.12.0 at least on the 6.x maintenance line |
Affected Software |
Earlier releases do not bundle the REST plugin and are not affected. |
Reporters | n0mi1k |
CVE Identifier | CVE-2026-104713 |
Problem
When an application uses the REST plugin, a request carrying a body has that body read into memory without any bound on how much will be accepted. A single request can therefore cause the server to allocate memory in proportion to the size of the request, exhausting the heap and denying service to other users.
This is the same class of issue as S2-072 and S2-073, in a component that was not covered by those fixes.
This issue is confined to the REST plugin, which is an optional component and not part of the Struts core. Applications that do not use the REST plugin are not affected. Unlike S2-072, no additional setting has to be enabled: applications using the plugin to accept request bodies are exposed in its default configuration.
Solution
Upgrade to Struts 7.4.0 at least.
Users remaining on the 6.x maintenance line should upgrade to Struts 6.12.0 at least, which carries the same fix.
Backward compatibility
No configuration or application changes are required for most applications.
The fixed releases limit the size of a request body the REST plugin will accept, at 2 MB (2,097,152 characters) by default. A request whose body exceeds the limit is rejected before the action is invoked; the rejection is raised as a Struts exception, which an application can map to a response of its choice with exception mapping. Applications that legitimately accept larger bodies through the plugin should raise the limit with the struts.rest.content.maxLength constant, given in characters, and remain protected by the higher bound.
Form submissions and multipart uploads are not parsed by the plugin and are unaffected by this limit.
Workaround
There is no configuration-only mitigation for this issue within Struts.
Users unable to upgrade immediately should enforce a maximum request body size ahead of the application, in the reverse proxy or the servlet container, for endpoints that accept request bodies.