Vantage6 Server JWT secret not cryptographically secure
Published Jun 12, 2025 · Updated Oct 23, 2026 · Also known as PYSEC-2025-221, GHSA-m3mq-f375-5vgh
Original summary
Normalized public record · Updated Oct 23, 2026
Vantage6 Server JWT secret not cryptographically secure
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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)
Potential 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
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 10%
- Aliases
- PYSEC-2025-221, GHSA-m3mq-f375-5vgh
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Jun 12, 2025 · Last refreshed Oct 23, 2026