CVE-2025-34351

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).

Published: 2025-11-26 Last update: 2025-12-09 Assigner: [email protected] Source: [email protected]

Conclusion & alert: This CVE is rejected; it is not tracked as an active vulnerability. Mandatory action: Do not treat as an active exposure for patching queues—follow the CVE record status and authoritative vendor or program statements only.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-34351

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-27 0.47%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-34351

CVSS metrics for this CVE.

No CVSS data in dataset for this CVE.

Weakness enumeration for CVE-2025-34351

GitHub Security Advisory for CVE-2025-34351

GHSA-gx77-xgc2-4888 · Severity: critical · Ecosystem: pip — Ray's New Token Authentication is Disabled By Default

Affected software / configurations for CVE-2025-34351

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-34351

URL Tags
No references in dataset.
cvelogic Threat Intelligence