How severe is GHSA-47w6-gwp4-w6vc?

No CVSS score has been assigned to GHSA-47w6-gwp4-w6vc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-47w6-gwp4-w6vc?

GHSA-47w6-gwp4-w6vc affects the following packages: vantage6 (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-47w6-gwp4-w6vc?

No patched version of vantage6 has shipped for GHSA-47w6-gwp4-w6vc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-47w6-gwp4-w6vc in my PyPI dependencies?

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

How do I mitigate GHSA-47w6-gwp4-w6vc if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-47w6-gwp4-w6vc actively exploited in the wild?

No public exploit code has been indexed for GHSA-47w6-gwp4-w6vc 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-47w6-gwp4-w6vc?

GHSA-47w6-gwp4-w6vc has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 26th 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 GHSA-47w6-gwp4-w6vc?

GHSA-47w6-gwp4-w6vc is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-47w6-gwp4-w6vc published, and has it been updated?

GHSA-47w6-gwp4-w6vc was published on July 24, 2026 and was last updated on August 19, 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

Not in CISA KEV

GHSA-47w6-gwp4-w6vc — vantage6

GHSA-47w6-gwp4-w6vc is a CWE-863 vulnerability in vantage6. No vendor fix is recorded yet; mitigation options are listed below.

vantage6: Algorithm developer can edit another developer's algorithm that is pending / under review

Also known asCVE-2026-73652PYSEC-2026-3703

Published

Jul 24, 2026

Updated

Aug 19, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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 GHSA-47w6-gwp4-w6vc.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍vantage6

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

vantage6 is an open-source infrastructure for privacy preserving analysis. In version 5.0.2 and earlier, the algorithm-store edit permission lacks an ownership check, allowing one algorithm developer to alter another developer's algorithm while it is pending or under review. The attacker can change metadata including the algorithm image or image tag, causing reviewers and nodes to trust a different image from the one originally submitted for approval. No fixed version is available as of this review.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`vantage6`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vantage6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of vantage6 has shipped for GHSA-47w6-gwp4-w6vc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Edit permission lacks ownership check, so another developer could alter metadata that is later trusted by nodes. Worst they could do is update the image or image tag. If that is not noted, another image is approved than the one actually under review ### Patches No ### Workarounds No

O3 Security · Impact-Aware SCA

Is GHSA-47w6-gwp4-w6vc in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works