dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-54533

MEDIUM · 6.9 CVSS v4.0 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A container isolation vulnerability in vantage6 versions prior to 5.0.0 allows malicious algorithms to access input and output files belonging to other algorithms running on the same node, breaking the isolation boundary between algorithm containers.

MitigationUpgrade to version 5.0.0 or later to patch the container isolation flaw. Alternatively, implement algorithm container verification and restriction policies to ensure only trusted algorithms execute on nodes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed vantage6 package version
    Run 'pip show vantage6' or 'pip list | grep vantage6' to view the installed package version. If using the vantage6 CLI, run 'vantage6 --version' or check the version in your Python environment.
    Affected if The version displayed is earlier than 5.0.0 (e.g., 4.x.x, 3.x.x)
  2. Confirm this is a vantage6 node installation
    Check your vantage6 configuration files or running services to determine if this installation includes node functionality (algorithm execution). Nodes are typically configured via a 'node' configuration file in the vantage6 configuration directory.
    Affected if This is a vantage6 node that runs algorithm containers for federated analysis
  3. Verify algorithm container execution is enabled
    Inspect the node configuration file (typically in ~/.vantage6/ or /etc/vantage6/) for the 'algorithm' or 'tasks' section. Confirm that algorithm execution is not explicitly disabled.
    Affected if Algorithm containers are enabled and the node is configured to run algorithms for collaboration tasks
  4. Check for file sharing configuration
    Look in the node configuration for settings related to input/output file sharing, shared volumes, or the 'data_dir'/'output_dir' paths that may be shared between algorithm containers.
    Affected if The node uses shared directories or volumes accessible by multiple algorithm containers

You are affected if your vantage6 node runs algorithm containers and the installed vantage6 version is earlier than 5.0.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 5.0.0 or later to patch the container isolation flaw. Alternatively, implement algorithm container verification and restriction policies to ensure only trusted algorithms execute on nodes.

Recommended fix High confidence

vantage6 version 5.0.0

  1. Upgrade vantage6 to version 5.0.0 or later to resolve the improper access control vulnerability
  2. As an alternative mitigation if immediate upgrade is not possible, verify and restrict the algorithm containers that are allowed to run on the node

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54533 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data