CVE-2026-82115: 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:01 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
Users should upgrade to Apache Wicket versions 8.20.0, 9.25.0, or 10.12.0 where this issue is fixed. As a workaround, applications can reject unauthorized WebSocket connections by registering an IWebSocketConnectionFilter via WebSocketSettings#setConnectionFilter(), or by explicitly repeating the authorization check at the start of each WebSocketResource callback.
Description
Apache Wicket versions 7.0.0 and later through 8.19.0, 9.24.0, and 10.11.0 contain a missing authorization check in the native WebSocket support. The WebSocketMessageBroadcastHandler directly invokes resource callbacks without consulting the configured authorization strategy, allowing authenticated users to access WebSocketResource callbacks without proper authorization enforcement. This can lead to unauthorized use of WebSocket resources if the application relies solely on the authorization strategy to restrict access. Fixed in versions 8.20.0, 9.25.0, and 10.12.0.