How severe is CVE-2026-43975?

CVE-2026-43975 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-43975?

CVE-2026-43975 affects the following packages: org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-43975?

A fix is available for CVE-2026-43975; check the affected-versions list above or the advisory for the patched release of org.apache.wicket:wicket-core, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2026-43975 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-43975 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-43975 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-43975 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-43975?

CVE-2026-43975 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-43975?

CVE-2026-43975 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-43975 published, and has it been updated?

CVE-2026-43975 was published on May 6, 2026 and was last updated on November 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2026-43975 — wicket-core

MEDIUMFix: apache/wicket#1432

CVE-2026-43975 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.apache.wicket:wicket-core. A fix is available for org.apache.wicket:wicket-core — see the affected versions and patch details below.

Apache Wicket: Possible malicious path traversal in FolderUploadsFileManager

Also known asGHSA-3gmf-p6r4-q8m6

Published

May 6, 2026

Updated

Nov 10, 2026

Affected

3 pkgs

Patched

1 / 3

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-43975.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

This issue affects Apache Wicket: from 8.0.0 through 8.17.0, from 9.0.0 through 9.22.0, from 10.0.0 through 10.8.0.

Users are recommended to upgrade to version 10.9.0, which fixes the issue.

Affected Packages

3 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.wicket:wicket-core`	≥ 8.0.0-M1	No fix
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M1	No fix
☕Maven	`org.apache.wicket:wicket-core`	≥ 10.0.0-M1&&< 10.9.0	10.9.0`org.apache.wicket:wicket-core:10.9.0`

Affected Products

1 product · 3 configurations

Application

wicketapache

≥ 10.0.0 && ≤ 9.22.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2026-43975; check the affected-versions list above or the advisory for the patched release of org.apache.wicket:wicket-core, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

FolderUploadsFileManager in Apache Wicket does not validate or sanitize the uploadFieldId parameter or the clientFileName before constructing file paths, allowing an unauthenticated attacker to write arbitrary files outside the intended upload directory or read files from arbitrary locations on the server. This issue affects Apache Wicket: from 8.0.0 through 8.17.0, from 9.0.0 through 9.22.0, from 10.0.0 through 10.8.0. Users are recommended to upgrade to version 10.9.0, which fixes the issue.

O3 Security · Impact-Aware SCA

Is CVE-2026-43975 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-22Path Traversal

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

wicket

6.3/10

Code-Review3/10

Maintained10/10

Branch-Protection3/10

Assessed Nov 2, 2026

Timeline

Disclosed

May 6, 2026

Last updated

Nov 10, 2026

Identifiers

CVE-2026-43975

GHSA-3gmf-p6r4-q8m6

References

Advisorygithub.com · CVE 2026 43975.json Advisorylists.apache.org · xp2jrdk6ppv1zcmxb4w1mk2lg1dw3hbr Advisorynvd.nist.gov · CVE 2026 43975 Fixgithub.com Webopenwall.com Webgithub.com · 72470983f689c61e6a6c0b7388ef955f23bb1e16 Packagegithub.com · wicket

Related vulnerabilities

Also affects wicket-core

This CVE is medium severity; 7 of 7 other CVEs affecting wicket-core are rated as high or higher (top: high).

CVE-2024-53299CVE-2021-23937CVE-2014-0043CVE-2016-6806CVE-2014-3526CVE-2014-7808CVE-2020-11976

Same weakness: CWE-22

This CVE is medium severity, in line with the other 1 CVE with CWE-22.

CVE-2026-102943Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 10, 2026

CVE-2026-43975 — wicket-core

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-43975 in your dependencies?