CVE-2026-82115

Apache Wicket: The configured authorization strategy is not applied to a shared WebSocketResource

Published Nov 1, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
Missing authorization in Apache Wicket.

org.apache.wicket.protocol.ws.api.WebSocketMessageBroadcastHandler, the request handler Wicket's native WebSocket support uses to deliver an incoming frame, resolves the shared resource named by the client's handshake parameter and calls WebSocketResource#onPayload() on it directly, without consulting IAuthorizationStrategy#isResourceAuthorized(). That method has a single enforcement point in the framework, org.apache.wicket.request.handler.resource.ResourceRequestHandler, which the WebSocket transport does not pass through, and WebSocketResource#respond() is final and empty. No route to a WebSocketResource therefore asks the configured authorization strategy whether the caller may use it, and an @AuthorizeResource annotation on such a class has no effect.

A caller needs a bound Wicket session and the name of the resource. The name is not a secret: Wicket writes it into the page that opens the connection. No page of the application is otherwise involved, because a request naming a resource is served with a throwaway page. All of the resource's callbacks are reached this way, including onConnect() and both onMessage() overloads, and what a callback pushes back through WebSocketRequestHandler goes to the caller's own connection.

An application is affected where it registers a WebSocketResource as a shared resource and relies on the authorization strategy to restrict it. What the caller gains is whatever that resource's callbacks do with a text or binary message of the caller's choosing. The connection is registered under the caller's own session, so it gives no access to another user's connection.

As a workaround, reject unauthorized connections with an IWebSocketConnectionFilter registered through WebSocketSettings#setConnectionFilter(), or repeat the authorization check at the start of each callback.

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

Analysis

AI-generated

Technical impact

The flaw in Apache Wicket’s WebSocket message broadcast handler allows a request handler to deliver incoming frames directly to a shared WebSocketResource without consulting the framework’s IAuthorizationStrategy. As a result, an authenticated user bound to a Wicket session can provide the public resource name, establish a WebSocket connection, and invoke any of the resource’s callbacks—including onConnect and the onMessage methods—without any access control check. This can lead to execution of arbitrary application logic or data manipulation within the scope of that user’s session.

Affected Systems

Apache Software Foundation’s Apache Wicket framework is affected for all supported releases from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0, and older unsupported releases from 7.0.0 onward. The vulnerability exists when a WebSocketResource is registered as a shared resource and relies on the framework’s configured authorization strategy to restrict access.

Risk and Exploitability

With a CVSS score of 6.3 the vulnerability is considered moderately severe. The EPSS score is not available and the vulnerability is not listed in CISA KEV, indicating no known widespread exploitation. The attack requires a valid Wicket session and the public resource name, both of which are accessible to an attacker from the client side. An attacker can send arbitrary message payloads over the established WebSocket connection, potentially triggering unintended application logic, but the connection remains scoped to the attacker’s own session and does not allow cross‑user session hijacking.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Wicket to version 8.20.0, 9.25.0, or 10.12.0 or a newer fix release.
  • Register an IWebSocketConnectionFilter via WebSocketSettings#setConnectionFilter() to reject any connections that fail the framework’s IAuthorizationStrategy check.
  • Insert an explicit authorization check at the start of each WebSocketResource callback to reinforce the intended security policy.

Generated by OpenCVE AI on November 1, 2026 at 23:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache wicket
Vendors & Products Apache
Apache wicket
Type Values Removed Values Added
Description Missing authorization in Apache Wicket. org.apache.wicket.protocol.ws.api.WebSocketMessageBroadcastHandler, the request handler Wicket's native WebSocket support uses to deliver an incoming frame, resolves the shared resource named by the client's handshake parameter and calls WebSocketResource#onPayload() on it directly, without consulting IAuthorizationStrategy#isResourceAuthorized(). That method has a single enforcement point in the framework, org.apache.wicket.request.handler.resource.ResourceRequestHandler, which the WebSocket transport does not pass through, and WebSocketResource#respond() is final and empty. No route to a WebSocketResource therefore asks the configured authorization strategy whether the caller may use it, and an @AuthorizeResource annotation on such a class has no effect. A caller needs a bound Wicket session and the name of the resource. The name is not a secret: Wicket writes it into the page that opens the connection. No page of the application is otherwise involved, because a request naming a resource is served with a throwaway page. All of the resource's callbacks are reached this way, including onConnect() and both onMessage() overloads, and what a callback pushes back through WebSocketRequestHandler goes to the caller's own connection. An application is affected where it registers a WebSocketResource as a shared resource and relies on the authorization strategy to restrict it. What the caller gains is whatever that resource's callbacks do with a text or binary message of the caller's choosing. The connection is registered under the caller's own session, so it gives no access to another user's connection. As a workaround, reject unauthorized connections with an IWebSocketConnectionFilter registered through WebSocketSettings#setConnectionFilter(), or repeat the authorization check at the start of each callback. 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 7.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.
Title Apache Wicket: The configured authorization strategy is not applied to a shared WebSocketResource
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 6, 2026, 2:45 PM
Reserved
Aug 28, 2026, 6:20 AM
Status
Deferred
Published
Nov 1, 2026, 10:17 PM
Modified
Nov 6, 2026, 3:17 PM