Skip to main content
CVE-2024-21649VulnerabilityPublished Updated

CVE-2024-21649: vantage6 · Code Injection

Affects vantage6Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 4.2.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.2.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade vantage6/vantage6 to 4.2.0.

Affected software

ProductAffectedFixed in
GitHubvantage6/vantage6pkg:github/vantage6/vantage6Other threatsAffected
  • <4.2.0
Fixed in
  • 4.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to vantage6 version 4.2.0 or later, where the vulnerability is patched. 2. Implement strict access controls and monitoring for vantage6 user accounts to prevent unauthorized authentication. 3. Employ multi-factor authentication (MFA) to reduce the risk of credential compromise. 4. Conduct regular audits of environment variable configurations and algorithm deployment parameters to detect anomalous or unauthorized changes. 5. Use network segmentation to isolate vantage6 servers from broader enterprise networks, limiting potential lateral movement in case of compromise. 6. Monitor system and application logs for unusual activity indicative of code injection attempts or exploitation. 7. Educate administrators and users about the risks of code injection and the importance of secure credential management. 8. If upgrading immediately is not feasible, consider temporary compensating controls such as restricting access to vantage6 interfaces and disabling non-essential features that accept environment variables.

Description

The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). Prior to 4.2.0, authenticated users could inject code into algorithm environment variables, resulting in remote code execution. This vulnerability is patched in 4.2.0.

References

Community reviews

Loading reviews…