# CVE-2026-82558: Apache Wicket missing authorization in WebSocketBehavior

Source: https://junglewise.ai/threats/cve-2026-82558-missing-authorization-in-apache-wicket-org-apache-wicket-protocol  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-01. Updated: 2026-11-01  
License: CC BY 4.0 with a link back

CVE-2026-82558 · Severity: info · Published 2026-11-01

Apache Wicket is a Java web framework that provides WebSocket support for real-time communication between server and client. A flaw in how Wicket handles WebSocket messages allows clients to invoke callbacks on components they should not have access to, such as hidden or disabled components protected by authorization rules. An attacker with their own session can send WebSocket messages to restricted components on their own pages, potentially bypassing intended access controls.

Technologies: [Apache Wicket](https://junglewise.ai/threats/technologies/apache-wicket). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## 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

## Related threats

- [Apache Wicket improper input neutralization in JavaScript generation](https://junglewise.ai/threats/cve-2026-95863-improper-neutralization-of-input-during-web-page-generation-in)
- [Apache Wicket missing Content-Security-Policy headers with nested request handler delegates](https://junglewise.ai/threats/cve-2026-87718-apache-wicket-10-10-0-10-11-0-and-9-24-0-do-not-set-the-content)
- [Apache Wicket ExternalLink reflected XSS in onclick attribute](https://junglewise.ai/threats/cve-2026-84231-improper-neutralization-of-input-during-web-page-generation-in)
- [Apache Wicket path validation bypass in package resource handling](https://junglewise.ai/threats/cve-2026-84177-incorrect-behavior-order-in-apache-wicket-a-file-path-is)
- [Apache Wicket template disclosure via class loader misconfiguration](https://junglewise.ai/threats/cve-2026-84172-files-accessible-to-external-parties-in-apache-wicket-org-apache)