CVE-2026-82705: Apache Wicket · Missing Authorization
Affects wicket-coreSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium · fixed in 8.20.0 : update wicket-core when convenient.
Data as of 2 Nov 2026, 01:00 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 8.20.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.wicket/wicket-corepkg:maven/org.apache.wicket/wicket-coreOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Wicket to version 8.20.0, 9.25.0, or 10.12.0 or later, where the issue is fixed. As a workaround, register resources in the application's shared resources and pass ResourceReference instances to components instead of IResource instances to ensure authorization checks are enforced.
Description
Apache Wicket versions 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, and 10.0.0 through 10.11.0 have a missing authorization enforcement issue. The framework's authorization strategy is bypassed when resources are served through certain components using IResource instances instead of ResourceReference, allowing unauthorized access to restricted resources. This affects applications that restrict resources via IAuthorizationStrategy or @AuthorizeResource annotations but use components that serve resources directly without the authorization check. The issue is fixed in versions 8.20.0, 9.25.0, and 10.12.0.