Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-18201 | Vantage6 Server JWT secret not cryptographically secure |
Github GHSA |
GHSA-m3mq-f375-5vgh | Vantage6 Server JWT secret not cryptographically secure |
Wed, 17 Sep 2025 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:vantage6:vantage6:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
Mon, 14 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Fri, 13 Jun 2025 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 12 Jun 2025 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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-generated key is a UUID1, which is not cryptographically secure as it is predictable to some extent. This vulnerability is fixed in 4.11.0. | |
| Title | Vantage6 Server JWT secret not cryptographically secure | |
| Weaknesses | CWE-330 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-06-13T14:06:06.347Z
Reserved: 2025-04-17T20:07:08.556Z
Link: CVE-2025-43866
Updated: 2025-06-13T14:06:00.500Z
Status : Analyzed
Published: 2025-06-12T18:15:20.713
Modified: 2025-09-17T18:44:19.670
Link: CVE-2025-43866
No data.
OpenCVE Enrichment
Updated: 2025-06-24T09:51:38Z
EUVD
Github GHSA