Quick answers
- Is CVE-2026-43975 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-43975 being exploited in the wild.
- How severe is CVE-2026-43975?
- Medium severity, with a CVSS score of 6.5, published 6 May 2026.
- Which products and versions are affected?
- Apache Software Foundation Wicket 8.0.0 through 8.17.0, 9.0.0 through 9.22.0, 10.0.0 through 10.8.0; org.apache.wicket:wicket-core (Maven) ECOSYSTEM:introduced=8.0.0-M1,last_affected=8.17.0.
- Is there a fix for CVE-2026-43975?
- A patch was published on 2026-04-27: Fix merged into master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-43975 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-43975?
- Check whether you run Apache Wicket, Apache Software Foundation Wicket or org.apache.wicket:wicket-core (Maven) 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.
Technical details
A path traversal vulnerability exists in the FolderUploadsFileManager component of Apache Wicket. The vulnerability stems from a failure to validate or sanitize the 'uploadFieldId' HTTP query parameter and the 'clientFileName' field within AJAX-based file upload requests. An unauthenticated remote attacker can use traversal sequences (e.g., '../') to escape the intended upload directory. This allows for arbitrary file writes, potentially leading to Remote Code Execution (RCE) via JSP webshells, and arbitrary file reads from the server's filesystem. The issue is fixed in version 10.9.0.
Affected products
- Apache Wicket 8.0.0 through 8.17.0, 9.0.0 through 9.22.0, 10.0.0 through 10.8.0
Identifiers
- CVE-2026-43975
- GHSA-3gmf-p6r4-q8m6
Timeline
- 2026-04-21: other: Vulnerability reported via pull request
- 2026-04-27: patched: Fix merged into master branch
- 2026-05-06: disclosed: Public advisory released
- 2026-05-06: advisory: NVD publication