CVE-2026-54445: Vantage6: Set admin user and password from environment or configuration
Impact Vantage6 currently provides an initial user with username root and password root. This is not ideal for the following reasons: - Attackers know that almost all vantage6 servers have a user with username root that probably has admin rights - The initial password is very weak and it is possible that administrators forget to reset it.
Published Jun 5, 2026 · Updated Jul 9, 2026
Affected packages
vantage6
- Ecosystem
- PyPI
- Affected
- <= 4.2.3
- Fixed in
- 5.0.0
- Check
pip show vantage6
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Vantage6 currently provides an initial user with username root and password root. This is not ideal for the following reasons:
- Attackers know that almost all vantage6 servers have a user with username
rootthat probably has admin rights - The initial password is very weak and it is possible that administrators forget to reset it.
Patches
No
Workarounds
It is possible to delete the root user after it has been used to create other users
References
We could consider doing this like mongodb
Additional info
Luis uses the following patch to mitigate it:
diff --git a/vantage6-server/vantage6/server/__init__.py b/vantage6-server/vantage6/server/__init__.py
index ea362c1e..c6dcbbd9 100644
--- a/vantage6-server/vantage6/server/__init__.py
+++ b/vantage6-server/vantage6/server/__init__.py
@@ -618,18 +618,30 @@ class ServerApp:
# TODO use constant instead of 'Root' literal
root = db.Role.get_by_name("Root")
- log.warn(
- f"Creating root user: "
- f"username={SUPER_USER_INFO['username']}, "
- f"password={SUPER_USER_INFO['password']}"
- )
+ # Temporary patch
+ # read initial root password from file (docker secret) if provided
+ # TODO: This is a workaround so we don't have an insecure vserver
+ # at the start. Ideally, we would provide an already hashed
+ # password. But as hashing is implemented via @validates on
+ # the field 'password', there isn't a nice way around this.
+ if os.environ.get("V6_INITIAL_ROOT_PASSWORD_FILE"):
+ with open(
+ os.environ.get("V6_INITIAL_ROOT_PASSWORD_FILE")
+ ) as password_file:
+ initial_root_password = password_file.read().strip()
+ log.info(
+ f"Creating root user with password provided via V6_INITIAL_ROOT_PASSWORD_FILE"
+ )
+ else:
+ initial_root_password = SUPER_USER_INFO["password"]
+ log.warn(f"Creating root user with default credentials!")
user = db.User(
username=SUPER_USER_INFO["username"],
roles=[root],
organization=org,
email="[email protected]",
- password=SUPER_USER_INFO["password"],
+ password=initial_root_password,
failed_login_attempts=0,
last_login_attempt=None,
)References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-73652
vantage6: Algorithm developer can edit another developer's algorithm that is pending / under review
high7.1No fixJul 24, 2026CVE-2024-24769
Vantage6: No limit on emails sent for password/MFA reset
low2.1Jun 5, 2026CVE-2024-27928
Vantage6: 2FA can be circumvented with hacked email access
medium5.9Jun 5, 2026CVE-2026-54533
vantage6 node has an Improper Access Control issue
medium6.9Jun 5, 2026CVE-2025-43863
vantage6 lacks brute-force protection on change password functionality
low1.7Jun 12, 2025CVE-2024-32969
vantage6 collaboration admins can extend their influence by expanding the collaboration
low2.7May 22, 2024
