Report: Full Disclosure mailing list, 2026-10-29,
https://seclists.org/fulldisclosure/2026/Nov/3
Disposition: VALID-HARDENING, fixed as WW-5846 (THREAT_MODEL.md section 13)
TLP:CLEAR

In short

The report is correct and the behaviour has been fixed. It was not a
vulnerability: the exemption list is empty by default and an empty list
never matched, so deployments that did not configure exemptions were fully
protected.

What the report describes

The Fetch Metadata, COOP and COEP interceptors compared each configured
exemptedPaths entry with the servlet context path instead of the request
path. An entry naming an action path therefore never matched, and an entry
equal to the context path matched every request and disabled the
interceptor for the whole application.

What the framework does with that input

- exemptedPaths is an operator setting; in the default configuration it is
empty (struts-default.xml), and the interceptors apply to every request.
- The interceptors now compare entries with the path of the request inside
the application, the servlet path plus the path info (RequestUtils.getUri
in FetchMetadataInterceptor and the COOP and COEP interceptors). The
documentation describes the old and the new behaviour.

Why this is not a vulnerability

The protections were enforced on every request unless an operator
configured an exemption. An exemption that was more than documented is a
hardening issue in a configured, non-default setting (THREAT_MODEL.md
sections 3 and 13).

What the project is doing

WW-5846 makes the interceptors compare exemptedPaths entries with the
request path, on both maintained lines. The change is in the public issue
tracker and the documentation.

What users should do

Operators who configured exemptedPaths should check their entries against
the documentation: an entry must be the request path inside the
application, for example /api/report, not the context path.

References

- https://issues.apache.org/jira/browse/WW-5846
- https://struts.apache.org/core-developers/fetch-metadata-interceptor.html
- https://github.com/apache/struts/blob/main/THREAT_MODEL.md
- https://github.com/apache/struts/blob/main/SECURITY.md

New evidence goes to [email protected]; questions about this
notice go to this list.

on behalf of the Apache Struts PMC
Ɓukasz

Reply via email to