Skip to main content
VulnerabilityPublished

CVE-2026-82559: Apache Wicket · Insufficient Session Expiration

Affects wicket-coreSource GCVE Database

0
Compare
Authoritative record:CVE-2026-82559· Low 2.3

Not known to be exploited · CVSS 2.3 Low · fixed in 8.20.0 : update wicket-core when convenient.

Data as of 2 Nov 2026, 01:00 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (apache)CVSS 4.02.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Mavenorg.apache.wicket/wicket-corepkg:maven/org.apache.wicket/wicket-coreOther threatsAffected
  • >=8.0.0 <=8.19.0
  • >=9.0.0 <=9.24.0
  • >=10.0.0 <=10.11.0
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, where this issue is fixed. If upgrading is not immediately possible, consider configuring the container to close WebSocket connections when the HTTP session is destroyed, if supported. Applications that do not use Wicket's native WebSocket support are not affected. No other specific mitigations are indicated by the vendor advisory.

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 as it was at connection time, detaching from the live container session. As a result, when the container invalidates the session (e.g., logout or timeout), the WebSocket connection continues to operate with the old session state, potentially allowing authorization decisions against revoked identities. This affects applications using Wicket's native WebSocket on authenticated pages where sessions are ended by the container rather than Wicket. Some containers may close WebSocket connections on session destruction, but this behavior is container-specific. The issue is fixed in Apache Wicket versions 8.20.0, 9.25.0, and 10.12.0.

References

Community reviews

Loading reviews…