Medium [CVE-2026-82115] Missing authorization in Apache Wicket
This medium-severity Apache Software Foundation advisory covers CVE-2026-82115 affecting Apache Wicket.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
See Apache Software Foundation's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
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.
- 8.0.0 through 8.19.0
- 9.0.0 through 9.24.0
- 10.0.0 through 10.11.0.
- through 10.11.0
Official advisory · high-confidence parse· fetched 9 hours ago·verify at source
- 8.20.0
- 9.25.0
- 10.12.0
Official advisory · high-confidence parse· fetched 9 hours ago·verify at source
Mitigation checklist
- Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
- An application is affected where it registers a WebSocketResource as a shared resource and relies on the authorization strategy to restrict it.
Official advisory · high-confidence parse· fetched 9 hours ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-111089Nov 1, 2026Apache Wicket reads texts from the application's resource bundles — a localized label
- CVE-2026-95863Nov 1, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-87718Nov 1, 2026Apache Wicket 10.10.0, 10.11.0 and 9.24.0 do not set the Content-Security-Policy headers
- CVE-2026-84231Nov 1, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-84177Nov 1, 2026Incorrect behavior order in Apache Wicket: a file path is validated before the framework
- CVE-2026-84172Nov 1, 2026Files accessible to external parties in Apache Wicket
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.