Quick answers
- Is CVE-2026-82558 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82558 being exploited in the wild.
- How severe is CVE-2026-82558?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, 10.0.0 through 10.11.0, and 6.0.0 through unsupported versions.
- Is there a fix for CVE-2026-82558?
- Yes: fixed in 8.20.0, 9.25.0, 10.12.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82558 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82558?
- Check whether you run Apache Wicket at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 8.20.0, 9.25.0, 10.12.0
Technical details
The WebSocketBehavior class fails to check authorization before invoking onMessage() callbacks, unlike the Ajax behavior which validates component visibility and enabled status through Behavior#canCallListener(). WebSocket messages are delivered to all WebSocketBehaviors on a page without authorization checks, allowing clients to interact with components restricted by IAuthorizationStrategy or annotations like @AuthorizeAction. An attacker requires their own session and page containing the vulnerable component, so cross-session attacks are not possible.
Affected products
- Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, 10.0.0 through 10.11.0, and 6.0.0 through unsupported versions
Timeline
- 2026-11-01: disclosed