CVE-2025-69277

libsodium before ad3004e, in atypical use cases involving certain custom cryptography or untrusted data to crypto_core_ed25519_is_valid_point, mishandles checks for whether an elliptic curve point is valid because it sometimes allows points that aren't in the main cryptographic group.

Published: 2025-12-31 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-69277 is rated Low Risk (20.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-69277

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 2026-06-15 0.01% 0.17% +0.15%
2 2025-12-31 — 0.01% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.4 2.7 [email protected]

Weakness enumeration for CVE-2025-69277

GitHub Security Advisory for CVE-2025-69277

GHSA-mrfv-m5wm-5w6w · Severity: medium · Ecosystem: composer — libsodium has Incomplete List of Disallowed Inputs

OS Trackers for CVE-2025-69277

vendor priority summary link
alpine medium CVE-2025-69277: 2 source package rows (libsodium, py3-pynacl); 15 state rows across 8 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-community, 3.23-main, edge-community, edge-main); fixed 9, open 6. https://security.alpinelinux.org/vuln/CVE-2025-69277
debian not yet assigned CVE-2025-69277 not yet assigned priority: Debian including 1 source packages (libsodium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-69277
redhat medium — https://access.redhat.com/security/cve/CVE-2025-69277
suse medium — https://www.suse.com/security/cve/CVE-2025-69277/
ubuntu medium CVE-2025-69277 medium priority: Ubuntu including 1 source packages (libsodium), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 5, needs-triage 3. https://ubuntu.com/security/CVE-2025-69277

Affected software / configurations for CVE-2025-69277

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-69277

cvelogic Threat Intelligence