Missing Authorization Affecting org.apache.wicket:wicket-core package, versions [8.0.0-M1,8.20.0)[9.0.0-M1,9.25.0)[10.0.0-M1,10.12.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHEWICKET-22150197
- published3 Nov 2026
- disclosed1 Nov 2026
- creditEmond Papegaaij
Introduced: 1 Nov 2026
NewCVE-2026-82705 (opens in a new tab)How to fix?
Upgrade org.apache.wicket:wicket-core to version 8.20.0, 9.25.0, 10.12.0 or higher.
Overview
org.apache.wicket:wicket-core is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favorite technology.
Affected versions of this package are vulnerable to Missing Authorization via the component resource handlers in ResourceLink, LocalizedImageResource, and AjaxDownloadBehavior. An attacker can retrieve restricted resource contents, including data-table exports, by requesting a component listener URL that serves an IResource directly; these paths call IResource.respond() without checking the configured IAuthorizationStrategy. The flaw affects applications that restrict resources with a custom strategy or @AuthorizeResource and pass those resources to ResourceLink, Image, ImageButton, AjaxDownloadBehavior, or ExportToolbar.
Workarounds
- Register the resource as an application shared resource and pass its
ResourceReferenceto the component instead of theIResource; this routes requests through authorization and prevents the component-listener path from bypassing the resource authorization strategy.