Live › vulnerability › CVE-2026-82558
Apache Wicket's WebSocketBehavior calls its message handlers without the authorization check that Ajax behaviors get, so a WebSocketBehavior on a hidden or disabled component receives messages from the client. An attacker with a session of their own can send messages that reach the application's handler and get a response written back to them, where the same component would refuse an Ajax call.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-01 22:22 UTC. All times on this page are UTC.
Applications that use Wicket's native WebSocket support and attach a WebSocketBehavior that overrides onMessage() to a component that is hidden, disabled, or restricted through an authorization strategy. The client must have its own session and a page containing that component; messages stay within the client's own session and page store. Applications without such behaviors, and those that only push messages from the server, are not affected.
No product ranges from the sources yet.
WebSocketBehavior subclasses that override onMessage() and check whether they are attached to components hidden, disabled, or restricted by an IAuthorizationStrategy, such as MetaDataRoleAuthorizationStrategy or @AuthorizeAction.8.20.09.25.010.12.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Missing authorization in Apache Wicket.
org.apache.wicket.protocol.ws.api.WebSocketBehavior, through which Wicket's native WebSocket support hands a message sent by the client to the application, calls its onMessage() callbacks without checking whether the client may invoke the component the behavior is attached to. Wicket opens a single WebSocket connection per page, and a message received on it is delivered to every WebSocketBehavior of that page. For an Ajax behavior Wicket makes this check before invoking it, through Behavior#canCallListener(Component), which refuses a component that is not visible or not enabled, including one for which the IAuthorizationStrategy denies the RENDER or ENABLE action. A WebSocketBehavior attached to such a component, or to a child of one, therefore receives the client's text and binary messages, together with a WebSocketRequestHandler that writes back to that client, where an Ajax behavior on the same component would be refused.
An application is affected where it attaches a WebSocketBehavior that overrides onMessage() to a component that it hides, disables, or restricts through its IAuthorizationStrategy, for example with MetaDataRoleAuthorizationStrategy or the AuthorizeAction annotation. The client needs a session of their own and a page of their own that contains such a component: messages are delivered only to pages in the page store of the client's own session, so this gives no access to another user's session, page or connection. Messages pushed by the server 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-82558")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.