CVE-2026-82559: Apache Wicket · DEPRECATED: Insufficient Session Expiration
Affects Apache WicketSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low · fixed in 8.20.0 : update Apache Wicket when convenient.
Data as of 1 Nov 2026, 22:30 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 8.20.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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 |
|---|---|---|
| Apache Wicketorg.apache.wicket:wicket-native-websocket-core | Affected
| Fixed in– |
Mavenorg.apache.wicket/wicket-native-websocket-corepkg:maven/org.apache.wicket/wicket-native-websocket-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 Apache Wicket to versions 8.20.0, 9.25.0, or 10.12.0 or later, where this issue is fixed. Applications that do not use Wicket's native WebSocket support are not affected. Some containers may mitigate this issue by closing WebSocket connections when the HTTP session is destroyed, but this behavior is container-specific and should not be relied upon as the sole mitigation.
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 suffer from insufficient session expiration in its native WebSocket support. The issue arises because the WebSocket connection uses a copy of the HTTP session made at connection time, which detaches it from the live container session. Consequently, invalidating the container session does not end the WebSocket connection, allowing the connection to continue operating with the old session state, including any authenticated identity. Some containers may close the WebSocket when the HTTP session ends, but this behavior is container-dependent. The vulnerability is fixed in Apache Wicket versions 8.20.0, 9.25.0, and 10.12.0.