How severe is CVE-2022-41920?

CVE-2022-41920 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-41920?

CVE-2022-41920 affects the following packages: github.com/duke-git/lancet/v2 (Go), github.com/duke-git/lancet (Go). Ecosystems affected: Go.

How do I fix CVE-2022-41920?

Update github.com/duke-git/lancet/v2 to 2.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41920 is resolved across your whole dependency graph.

How do I detect CVE-2022-41920 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/duke-git/lancet/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-41920 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-2022-41920 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-41920, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-41920?

CVE-2022-41920 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th 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-2022-41920?

CVE-2022-41920 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-2022-41920 published, and has it been updated?

CVE-2022-41920 was published on November 17, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2022-41920 — lancet

MEDIUMFix: duke-git/lancet@f133b32

CVE-2022-41920 is a medium-severity (CVSS 6.3) Path Traversal vulnerability in github.com/duke-git/lancet/v2. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/duke-git/lancet/v2 — see the affected versions and patch details below.

Zip slip in Lancet

Also known asGHSA-pp3f-xrw5-q5j4GO-2022-1114

Published

Nov 17, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-41920.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% 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

2 pkgs affected

🐹github.com/duke-git/lancet/v2🐹github.com/duke-git/lancet

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

Description

Impact

What kind of vulnerability is it? Who is impacted?

ZipSlip issue when use fileutil package to unzip files.

Patches

Has the problem been patched? What versions should users upgrade to?

It will fixed in v2.1.10, Please upgrade version to v2.1.10 or above. Users who use v1.x.x should upgrade v1.3.4 or above.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

No, users have to upgrade version.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/duke-git/lancet/v2`	≥ 2.0.0&&< 2.1.10	2.1.10`go get github.com/duke-git/lancet/v2@v2.1.10`
🐹Go	`github.com/duke-git/lancet`	all versions	1.3.4`go get github.com/duke-git/lancet@v1.3.4`

Affected Products

1 product · 2 configurations

Application

lancetlancet_project

≥ 2.0.0 && < 2.1.10

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Lancet is a general utility library for the go programming language. Aff…

github.comNVDNov 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/duke-git/lancet/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/duke-git/lancet/v2 to 2.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41920 is resolved across your whole dependency graph.
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

### Impact _What kind of vulnerability is it? Who is impacted?_ ZipSlip issue when use fileutil package to unzip files. ### Patches _Has the problem been patched? What versions should users upgrade to?_ It will fixed in v2.1.10, Please upgrade version to v2.1.10 or above. Users who use v1.x.x should upgrade v1.3.4 or above. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ No, users have to upgrade version.