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](https://docs.python.org/3/library/uuid.html#uuid.uuid1) ### Patches No ### Workarounds You may define JWT secret key in the server configuration file
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-43866US | high7.5OT elevated | — | ||
vantage6 is an open-source infrastructure for privacy preserving analysis. The JWT secret key in the vantage6 server is auto-generated unless defined by the user. The auto-generate… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/pypa/advisory-database/tree/main/vulns/vantage6-server/PYSEC-2025-221.yamlWEB
- https://github.com/vantage6/vantage6PACKAGE
- https://github.com/vantage6/vantage6/commit/e39a262faf1cd4c554bf1b8e57eeea082da995c0WEB
- https://github.com/vantage6/vantage6/security/advisories/GHSA-m3mq-f375-5vghWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-43866ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan