CVE-2026-71378: Apache Wicket: Cross-Site Request Forgery (CSRF) protection bypass in ResourceIsolationRequestCycleListener

Published Aug 30, 2026
·
Updated

ResourceIsolationRequestCycleListener protects a Wicket application against cross-site request forgery by rejecting requests that a resource isolation policy judges to come from another origin. Its default policy, FetchMetadataResourceIsolationPolicy, was derived from a reference implementation written to guard static resources, and it inherited two allowances that are unsafe when the thing being guarded is an action on a page: Every "simple top-level navigation" was allowed. Any GET request carrying Sec-Fetch-Mode: navigate whose Sec-Fetch-Dest was neither object nor embed was allowed, whatever Sec-Fetch-Site said — including cross-site. Wicket invokes component listeners (Link.onClick(), form submits, behaviour callbacks) through ordinary GET navigations, so a page under an attacker's control could navigate the victim's browser to a listener URL and have that listener run inside the victim's authenticated session. Browsers send SameSite=Lax cookies — the effective default when no SameSite attribute is set — on cross-site top-level GET navigations, so the victim's session cookie accompanied the request. Sec-Fetch-Site: same-site was allowed unconditionally. That value means the same registrable domain and scheme but a different origin — another subdomain or another port. Any sibling origin could therefore invoke any listener by any method, POST form submits included, and cookies are always sent on same-site requests regardless of SameSite. A hostile sibling origin obtained through a subdomain takeover, through delegated user content, or through an XSS elsewhere on the site could act as the authenticated user. Users are recommended to upgrade to version 9.24.0 or 10.11.0, which fix the issue. Affected versions

Apache Wicket 9.1.0 through 9.23.0 Apache Wicket 10.0.0 through 10.10.0

Not affected

Any release older than 9.1.0: Apache Wicket 8.x (8.0.0 through 8.17.0). The resource isolation classes do not exist in the 8.x line, which offers only the Origin/Referer-based CsrfPreventionRequestCycleListener. No 8.x release requires a fix. Apache Wicket 9.0.0. ResourceIsolationRequestCycleListener and FetchMetadataResourceIsolationPolicy were introduced by WICKET-6786 and first shipped in 9.1.0 (released 2020-10-07).

Affected Software

2 affected components
Apache wicket>=9.1.0<=9.23.0
Apache wicket>=10.0.0<=10.10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Wicket to a version that resolves this vulnerability.

    Fixed in 9.24.0
  2. Upgrade

    Upgrade Apache Wicket to a version that resolves this vulnerability.

    Fixed in 10.11.0

Event History

Aug 31, 2026
CVE Published
via MITRE·11:46 AM
Data Sourced
via MITRE·11:46 AM
DescriptionWeakness
Data Sourced
via NVD·12:17 PM
DescriptionWeakness

Frequently Asked Questions

1

Are applications using the default resource isolation policy affected?

Yes. The default FetchMetadataResourceIsolationPolicy allows simple top-level GET navigations regardless of Sec-Fetch-Site and also unconditionally allows requests marked Sec-Fetch-Site: same-site.

2

What must an attacker do to trigger the issue?

An attacker needs to cause a victim’s browser to perform a top-level GET navigation to a Wicket component-listener URL, such as one used by Link.onClick(), a form submission, or a behavior callback. The listener can then execute in the victim’s authenticated session.

3

Why can the request carry an authenticated session?

Browsers send SameSite=Lax cookies, including the effective default when no SameSite attribute is set, on cross-site top-level GET navigations. As a result, the victim’s session cookie can accompany the attacker-triggered request.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203