CVE-2026-54533
MediumCVSS 6.9Exploitation Probability (EPSS)
Low risk20th percentile - higher than 20% of all known CVEs
Summary
In versions prior to 5.0.0 of vantage6, malicious algorithms can potentially access other algorithms' input and output files. The issue is fixed in version 5.0.0.
Risk Assessment
The organization may be exposed to unauthorized access to data processed by algorithms, potentially leading to privacy and data security breaches.
Recommendation
It is recommended to upgrade to version 5.0.0 and to verify and restrict the algorithm containers that are allowed to run on the node.
Other vulnerabilities in vantage6
See all- CVE-2026-73652High
vantage6 version 5.0.2 and earlier has an algorithm-store edit permission lacking 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. No fixed version is available as of this review.
- CVE-2026-54445Medium
In versions prior to 5.0.0 of the vantage6 software, the default user `root` with the password `root` poses a significant security risk. Attackers can easily gain access to the system as many vantage6 servers have this user with admin rights.
- CVE-2024-27928Medium
In versions prior to 5.0.0 of the vantage6 software, an attacker who gains access to a user's email account can reset the password and the 2FA token via email, reducing security to a single authentication factor (email access). Version 5.0.0 fixes this issue.
- CVE-2024-24769Low
In versions prior to 5.0.0, users can reset their MFA tokens via API routes that send them emails. The number of emails sent is not limited, allowing attackers to flood users' mailboxes.
Original NVD description (English source)
vantage6 is an open-source infrastructure for privacy preserving analysis. Prior to version 5.0.0, malicious algorithms can potentially access other algorithms input and output files. Version 5.0.0 fixes the issue. As a workaround, verify and restrict the algorithm containers that are allowed to run on the node.