Quick answers
- Is CVE-2026-82956 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82956 being exploited in the wild.
- How severe is CVE-2026-82956?
- 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-82956?
- 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-82956 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82956?
- 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 vulnerability is an improper neutralization of input (CWE-79 stored XSS) in the AjaxNewWindowNotifyingBehavior component. The behaviour captures the browser's window.name parameter and stores it in the page's serialized state without validation. When the page is later rendered, the stored value is embedded directly into a JavaScript string literal without escaping, allowing an attacker-controlled window name containing a quote character to break out of the string and inject arbitrary JavaScript that runs with the application's origin privileges.
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: disclosed
- 2026-11-01: patched