CVE-2025-43866: Vantage6 Server JWT secret not cryptographically secure
Impact The JWT secret key in the vantage6 server is auto-generated unless defined by the user. The auto-generated key is a UUID1, which is not cryptographically secure as it is predictable to some extent Patches No Workarounds You may define JWT secret key in the server configuration file
Published Jun 12, 2025 · Updated Jun 8, 2026
Affected packages
vantage6-server
- Ecosystem
- PyPI
- Affected
- < 4.11.0
- Fixed in
- 4.11.0
- Check
pip show vantage6-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The JWT secret key in the vantage6 server is auto-generated unless defined by the user. The auto-generated key is a UUID1, which is not cryptographically secure as it is predictable to some extent
Patches
No
Workarounds
You may define JWT secret key in the server configuration file
References
- https://github.com/vantage6/vantage6/security/advisories/GHSA-m3mq-f375-5vgh
- https://nvd.nist.gov/vuln/detail/CVE-2025-43866
- https://github.com/vantage6/vantage6/commit/e39a262faf1cd4c554bf1b8e57eeea082da995c0
- https://github.com/pypa/advisory-database/tree/main/vulns/vantage6-server/PYSEC-2025-221.yaml
- https://github.com/advisories/GHSA-m3mq-f375-5vgh
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
