Quick answers
- Is CVE-2026-84177 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84177 being exploited in the wild.
- How severe is CVE-2026-84177?
- 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-84177?
- Yes: fixed in Wicket 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-84177 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84177?
- 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: Wicket 8.20.0, 9.25.0, 10.12.0
Technical details
The vulnerability stems from incorrect ordering: PackageResource validates a file path before the framework appends style, variation, and locale attributes (separated by underscores) that complete the final file name. PackageResourceGuard refuses markup templates by checking for a corresponding class file, but if the class name contains underscores (like Report_v2), an attacker can request a shorter base name that the guard accepts, then supply URL parameters to complete the path into a protected template. This affects only components with underscored class names where no shorter part is itself a class, and exposure is read-only access to HTML templates within the component's package.
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