Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
2.3

CVE-2026-82558: Apache Wicket can send WebSocket messages to hidden components

CVE-2026-82558 · published 20 days ago
Summary

If your Apache Wicket application uses WebSocket features and attaches a WebSocket handler to a page element that you have hidden, disabled, or otherwise restricted, the framework may still deliver client‑sent messages to that element. This can allow users to trigger code that should be inaccessible, potentially exposing information or actions. Fix it by not attaching WebSocket handlers to components that are not visible or authorized, and add your own checks before processing any incoming messages.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
apache software foundation apache wicket <= 8.19.0
Original advisory text
Apache Wicket: WebSocketBehavior delivers client messages to a component the client may not invoke
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.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
2.3 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-862Missing Authorization
Timeline
Published1 Nov 2026
Updated22 Nov 2026
First seen1 Nov 2026
Sources
CVE-2026-82558 · MITRE
Track software like this
Free during beta