CVE-2026-82705: Apache Wicket missing authorization in resource handlers

CVE-2026-82705 · Severity: info · Published 2026-11-01

Apache Wicket is a web application framework that manages access controls through authorization checks. A flaw in how Wicket enforces these authorization rules means that resources delivered through certain components—such as images, links, and file downloads—can bypass the intended access checks, allowing unauthorized access to restricted content that should require permission to view.

Technologies: Apache Wicket. Vendors: Apache.

Quick answers

Is CVE-2026-82705 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-82705 being exploited in the wild.
How severe is CVE-2026-82705?
Informational severity, published 1 November 2026.
Which products and versions are affected?
Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, 10.0.0 through 10.11.0.
Is there a fix for CVE-2026-82705?
Yes: fixed in Wicket 8.20.0, 9.25.0, 10.12.0. Until then: Register the resource in the application's shared resources and pass the resulting ResourceReference to the component instead of the IResource; this ensures the request is routed through the authorization handler. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82705 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-82705?
Check whether you run Apache Wicket at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Wicket 8.20.0, 9.25.0, 10.12.0

Register the resource in the application's shared resources and pass the resulting ResourceReference to the component instead of the IResource; this ensures the request is routed through the authorization handler.

Technical details

The vulnerability exists in org.apache.wicket.request.handler.resource.ResourceRequestHandler, which is the sole enforcement point for IAuthorizationStrategy.isResourceAuthorized(). Components including ResourceLink, Image, ImageButton, and AjaxDownloadBehavior can call IResource.respond() directly without triggering authorization checks when instantiated with an IResource rather than a ResourceReference. The authorization bypass is constructor-dependent rather than visible to the application, making it easy to introduce unintentionally.

Affected products

  • Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, 10.0.0 through 10.11.0

Timeline

  • 2026-11-01: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.