Missing Authorization Affecting org.apache.wicket:wicket-native-websocket-core package, versions [8.0.0-M1,8.20.0)[9.0.0-M1,9.25.0)[10.0.0-M1,10.12.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHEWICKET-22150196
- published3 Nov 2026
- disclosed1 Nov 2026
- creditEmond Papegaaij
Introduced: 1 Nov 2026
NewCVE-2026-82558 (opens in a new tab)How to fix?
Upgrade org.apache.wicket:wicket-native-websocket-core to version 8.20.0, 9.25.0, 10.12.0 or higher.
Overview
Affected versions of this package are vulnerable to Missing Authorization via the onEvent() dispatch in WebSocketBehavior. A client with their own session and page can send text or binary WebSocket messages that invoke onMessage() callbacks attached to hidden, disabled, or authorization-restricted components, bypassing the checks applied to Ajax listeners. The callback receives a WebSocketRequestHandler it can use to respond to the client, so these component restrictions do not prevent client-triggered callback processing.
Notes
- At the delivery step, client messages reach behaviors only on pages in the attacker’s own session; they do not reach another user’s session, page, or WebSocket connection.
- The flaw affects client-originated text and binary
onMessage()callbacks; server-pushed messages and other server notifications are unaffected.