Quick answers
- Is CVE-2026-82704 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82704 being exploited in the wild.
- How severe is CVE-2026-82704?
- 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.
- Is there a fix for CVE-2026-82704?
- 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-82704 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82704?
- 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
ListenerRequestHandler fails to enforce authorization when a listener URL omits the page identifier, causing a new page instance to be constructed without running Component#configure(). This skips the authorization flag check that normally blocks unauthorized listeners. Stateless pages are particularly vulnerable since Wicket itself generates listener URLs without page identifiers for them. The vulnerability affects components restricted via IAuthorizationStrategy (including role-based decorators) or Component#onConfigure() visibility/enabled flags.
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
Timeline
- 2026-11-01: advisory