---
id: "CVE-2026-82559"
kind: "vulnerability"
aliases: ["CVE-2026-82559"]
title: "Apache Wicket: WebSocket connections outlive ended sessions and keep their access"
severity: "low"
cvss: 2.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-wicket", "java", "package", "web-framework", "websocket"]
not_affected_if: ["no-native-websocket", "sessions-ended-by-wicket", "static-export"]
published_at: "2026-11-01T22:17:47+00:00"
first_seen_at: "2026-11-01T22:22:23+00:00"
updated_at: "2026-11-01T22:22:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82559", "first_seen_at": "2026-11-01T22:22:23+00:00"}]
---

# Apache Wicket: WebSocket connections outlive ended sessions and keep their access

Apache Wicket's native WebSocket support copies the container session when a connection opens, so ending the HTTP session does not end the WebSocket connection. The connection keeps resolving the old session, including its signed-in state, so an attacker holding an open connection can keep acting as a revoked user.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Wicket version in the project's build file or dependency tree, for example `mvn dependency:tree | grep wicket` or `gradle dependencies`.
- Search the code for `WebSocketBehavior` or `WebSocketResource` to see if native WebSocket support is used on pages or resources that require login.
- Check whether sessions are ended by the container (filters, container logout, idle timeout) rather than by Wicket.

## Fix

- Upgrade Apache Wicket 8.x to `8.20.0`
- Upgrade Apache Wicket 9.x to `9.25.0`
- Upgrade Apache Wicket 10.x to `10.12.0`

## Timeline

- 2026-11-01T22:22:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-82559

## From the sources

Insufficient session expiration in Apache Wicket.

org.apache.wicket.protocol.ws.WebSocketSettings#newWebSocketRequest() wraps the WebSocket upgrade request in an org.apache.wicket.protocol.ws.api.ServletRequestCopy, which is kept for the life of the connection and used to build the request for every frame that arrives on it. Copying the request is deliberate and is documented as such, because the container recycles the upgrade request once the handshake is over. The container session is copied along with it, into an org.apache.wicket.protocol.ws.api.HttpSessionCopy holding the session attributes as they stood when the connection was opened. That second copy is not necessary, because a session, unlike a request, is not discarded at the end of a request. Every frame afterwards resolves its Wicket session through ISessionStore#lookup(), which reads it out of the copy, so the connection is detached from the live container session for as long as it stays open.

Ending the session through the container therefore does not end the connection. After an idle timeout, an HttpSession#invalidate() call made from a filter or from a security framework, a container-managed logout, or a session replacement, the connection goes on resolving the org.apache.wicket.Session instance that existed when it was opened, together with that session's attributes and, for applications built on wicket-auth-roles, the signed-in state held on that same instance, so an authorization decision taken inside a WebSocket callback is taken against an identity that has already been revoked. The copy is also what the connection writes through: a Session#invalidateNow() issued from inside a WebSocket callback invalidates the copy and leaves the container session valid, and session attributes set over the connection are written to the copy rather than to the session.

An application is affected where it uses Wicket's native WebSocket support on pages or shared resources that require an authenticated session, and where sessions are ended by the container rather than by Wicket. Session#invalidateNow(), and AuthenticatedWebSession#invalidate() and #signOut() which call it, remain effective for a WebSocketBehavior on a page: they clear the page manager, and the connection can then no longer resolve the page it was opened for. A WebSocketResource is not limited in that way, because a frame naming a resource is served against a throwaway page and never consults the page manager, so such a connection outlives Wicket's own sign-out as well. Some containers close WebSocket connections themselves when the HTTP session they were opened under is destroyed, in which case the connection ends regardless; that is a property of the container rather than of Wicket. Applications that do not use the native WebSocket support are not affected.

This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0. Older, unsupported releases from 6.0.0 onwards are also affected. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_