How severe is GHSA-hgc3-hp6x-wpgx?

GHSA-hgc3-hp6x-wpgx has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hgc3-hp6x-wpgx?

GHSA-hgc3-hp6x-wpgx affects the following packages: antilles-tools (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-hgc3-hp6x-wpgx?

Update antilles-tools to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hgc3-hp6x-wpgx is resolved across your whole dependency graph.

How do I detect GHSA-hgc3-hp6x-wpgx in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for antilles-tools. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hgc3-hp6x-wpgx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hgc3-hp6x-wpgx?

O3 pinpoints whether GHSA-hgc3-hp6x-wpgx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hgc3-hp6x-wpgx actively exploited in the wild?

No public exploit code has been indexed for GHSA-hgc3-hp6x-wpgx 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 GHSA-hgc3-hp6x-wpgx?

GHSA-hgc3-hp6x-wpgx has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 78th 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.

When was GHSA-hgc3-hp6x-wpgx published, and has it been updated?

GHSA-hgc3-hp6x-wpgx was published on November 3, 2021 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-hgc3-hp6x-wpgx

HIGH

Antilles Dependency Confusion Vulnerability

Also known asCVE-2021-3840PYSEC-2021-840

Published

Nov 3, 2021

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk78th percentile+0.79%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍antilles-tools

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

Description

Potential Impact:

Remote code execution.

Scope of Impact:

Open-source project specific.

Summary Description:

A dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi). MITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known public repository such as PyPi. The configuration has been updated to only install components built by Antilles, removing all other public package indexes. Additionally, the antilles-tools dependency has been published to PyPi.

Mitigation Strategy for Customers (what you should do to protect yourself):

Remove previous versions of Antilles as a precautionary measure and Update to version 1.0.1 or later.

Acknowledgement:

The Antilles team thanks Kotko Vladyslav for reporting this issue.

References:

https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`antilles-tools`	all versions	1.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for antilles-tools. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update antilles-tools to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hgc3-hp6x-wpgx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hgc3-hp6x-wpgx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hgc3-hp6x-wpgx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Potential Impact: Remote code execution. ### Scope of Impact: Open-source project specific. ### Summary Description: A dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi). MITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known publ

O3 Security · Impact-Aware SCA

Is GHSA-hgc3-hp6x-wpgx in your dependencies?

O3 detects GHSA-hgc3-hp6x-wpgx across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works