How severe is GHSA-vc3v-ppc7-v486?

GHSA-vc3v-ppc7-v486 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vc3v-ppc7-v486?

GHSA-vc3v-ppc7-v486 affects the following packages: vantage6-server (PyPI), vantage6-node (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-vc3v-ppc7-v486?

Update vantage6-server to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vc3v-ppc7-v486 is resolved across your whole dependency graph.

How do I detect GHSA-vc3v-ppc7-v486 in my PyPI dependencies?

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

How do I mitigate GHSA-vc3v-ppc7-v486 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.

Is GHSA-vc3v-ppc7-v486 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vc3v-ppc7-v486 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-vc3v-ppc7-v486?

GHSA-vc3v-ppc7-v486 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th 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-vc3v-ppc7-v486?

GHSA-vc3v-ppc7-v486 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vc3v-ppc7-v486 published, and has it been updated?

GHSA-vc3v-ppc7-v486 was published on November 14, 2023 and was last updated on September 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.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

vantage6-server node accepts non-whitelisted algorithms from malicious serverGHSA-vc3v-ppc7-v486

HIGHFix: vantage6/vantage6@bf83521

GHSA-vc3v-ppc7-v486 is a high-severity (CVSS 7.2) CWE-345 vulnerability in vantage6-server. A fix is available for vantage6-server — see the affected versions and patch details below.

Also known asCVE-2023-47631PYSEC-2023-303PYSEC-2023-304

Published

Nov 14, 2023

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

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

🐍vantage6-server🐍vantage6-node

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 a framework to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). In affected versions a node does not check if an image is allowed to run if a parent_id is set. A malicious party that breaches the server may modify it to set a fake parent_id and send a task of a non-whitelisted algorithm. The node will then execute it because the parent_id that is set prevents checks from being run. This impacts all servers that are breached by an expert user. This vulnerability has been patched in version 4.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`vantage6-server`	all versions	4.1.2`pip install --upgrade 'vantage6-server==4.1.2'`
🐍PyPI	`vantage6-node`	all versions	4.1.2`pip install --upgrade 'vantage6-node==4.1.2'`

Affected Products

1 product · 2 configurations

Application

vantage6vantage6

< 4.1.2

1 version

4.1.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vantage6-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vantage6-server to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vc3v-ppc7-v486 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.

Frequently Asked Questions

### Impact A node does not check if an image is allowed to run if a `parent_id` is set. A malicious party that breaches the server may modify it to set a fake `parent_id` and send a task of a non-whitelisted algorithm. The node will then execute it because the `parent_id` that is set prevents checks from being run. Relevant node code [here](https://github.com/vantage6/vantage6/blob/version/4.1.1/vantage6-node/vantage6/node/docker/docker_manager.py#L265-L268) This impacts all servers that are breached by an expert user ### Patches Fixed in v4.1.2 ### Workarounds None