CVE-2025-69277

MEDIUMNVD 4.54.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
4.5
EG Score
4.5(medium)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity45% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

December 31, 2025

Last Modified

April 15, 2026

Advisory Details (8)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit.
generic Patch Available

[SECURITY] [DLA 4435-1] libsodium security update

https://lists.debian.org/debian-lts-announce/2026/01/msg00004.html
generic

A Vulnerability in Libsodium | Hacker News

https://news.ycombinator.com/item?id=46435614
generic

Things that use Ed25519

https://ianix.com/pub/ed25519-deployment.html
generic

Security: Fix CVE-2025-69277 · Issue #920 · pyca/pynacl · GitHub

https://github.com/pyca/pynacl/issues/920
github_commit

commit ecf41f55a3d8 (pyca/pynacl)

Fix landed in pyca/pynacl commit ecf41f55a3d8 — awaiting tagged release

https://github.com/pyca/pynacl/commit/ecf41f55a3d8f1e10ce89c61c4b4d67f3f4467cf
github_commit

commit 96314884d88d (pyca/pynacl)

Fix landed in pyca/pynacl commit 96314884d88d — awaiting tagged release

https://github.com/pyca/pynacl/commit/96314884d88d1089ff5f336dba61d7abbcddbbf7
github_commit

commit ad3004ec8731 (jedisct1/libsodium)

Fix landed in jedisct1/libsodium commit ad3004ec8731 — awaiting tagged release

https://github.com/jedisct1/libsodium/commit/ad3004ec8731730e93fcfbbc824e67eadc1c1bae
generic

A vulnerability in libsodium - Frank DENIS random thoughts.

https://00f.net/2025/12/30/libsodium-vulnerability/

Vendor Advisories for CVE-2025-69277(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibsodium23 (1.0.18-1ubuntu0.22.04.1) @ jammy2026-05-21ubuntu
redhatlibsodium-main-1.0.22-1.hum12026-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 11 ecosystems)
PyPI(2)
PackageVulnerable rangeFixed inDependents
hdwallet0.1.0 ... 3.6.0 (32 versions)3.6.1—
pynacl0.1.0 ... 1.6.1 (18 versions)1.6.2—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
libsodium—1.0.19-r1—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
libsodium—1.0.20-r1—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
libsodium—1.0.20-r1—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
libsodium—1.0.20-r1—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
libsodium—1.0.20-r1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libsodium1.0.18-11.0.18-1+deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libsodium1.0.18-11.0.18-1+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libsodium1.0.18-11.0.18-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libsodium1.0.18-11.0.18-2—
Packagist(1)
PackageVulnerable rangeFixed inDependents
paragonie/sodium_compatv0.1.0 ... v1.9.4 (73 versions)1.24.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:30 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-15 03:10 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-11 09:36 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-08-31 23:34 UTCOSV refresh
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:45 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 14:16 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:46 UTCEPSS rescore
  5. 2026-08-16 14:55 UTCEPSS rescore
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-15 00:26 UTCEG score recompute
  9. 2026-08-15 00:26 UTCVendor advisory
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-11 13:42 UTCEPSS rescore
  12. 2026-08-10 23:59 UTCEPSS rescore
  13. 2026-08-09 22:14 UTCEG score recompute
  14. 2026-08-09 22:14 UTCVendor advisory
  15. 2026-08-09 13:46 UTCEPSS rescore
  16. 2026-08-08 16:36 UTCEPSS rescore
  17. 2026-08-08 04:19 UTCEG score recompute
  18. 2026-08-08 04:19 UTCVendor advisory
  19. 2026-08-07 16:27 UTCEPSS rescore
  20. 2026-08-06 13:46 UTCEPSS rescore
  21. 2026-08-06 06:36 UTCEG score recompute
  22. 2026-08-06 06:36 UTCVendor advisory
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 10:37 UTCEPSS rescore
  25. 2026-08-03 10:35 UTCEPSS rescore
  26. 2026-08-02 02:26 UTCEPSS rescore
  27. 2026-08-01 04:15 UTCEPSS rescore
  28. 2026-07-30 16:27 UTCEPSS rescore
  29. 2026-07-30 01:30 UTCEPSS rescore
  30. 2026-07-27 14:13 UTCEPSS rescore
  31. 2026-07-27 02:39 UTCOSV refresh
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-25 14:17 UTCEPSS rescore
  35. 2026-07-25 14:17 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 03:02 UTCEG score recompute
  40. 2026-07-22 14:08 UTCEPSS rescore
  41. 2026-07-21 15:24 UTCEPSS rescore
  42. 2026-07-20 17:08 UTCEPSS rescore
  43. 2026-07-19 14:30 UTCEPSS rescore
  44. 2026-07-19 14:30 UTCEPSS rescore
  45. 2026-07-19 02:28 UTCEPSS rescore
  46. 2026-07-19 02:28 UTCEPSS rescore
  47. 2026-07-16 17:02 UTCEPSS rescore
  48. 2026-07-16 17:02 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-13 06:12 UTCEPSS rescore
  54. 2026-07-12 05:46 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-09 21:17 UTCOSV refresh
  59. 2026-07-09 19:10 UTCEPSS rescore
  60. 2026-07-08 15:15 UTCEPSS rescore
  61. 2026-07-07 13:46 UTCEPSS rescore
  62. 2026-07-06 16:27 UTCEPSS rescore
  63. 2026-07-04 06:31 UTCEPSS rescore
  64. 2026-07-04 06:31 UTCEPSS rescore
  65. 2026-07-01 15:06 UTCEPSS rescore
  66. 2026-06-30 23:22 UTCEPSS rescore
  67. 2026-06-30 23:22 UTCEPSS rescore
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-29 14:06 UTCEPSS rescore
  70. 2026-06-28 14:07 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-27 03:08 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-69277?
CVE-2025-69277 is a medium vulnerability published on December 31, 2025. libsodium before ad3004e, in atypical use cases involving certain custom cryptography or untrusted data to cryptocoreed25519isvalid_point, mishandles checks for whether an elliptic curve point is valid because it sometimes allows points that aren't in the main cryptographic group.
When was CVE-2025-69277 disclosed?
CVE-2025-69277 was first published in the National Vulnerability Database on December 31, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69277 actively exploited?
CVE-2025-69277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.7% of all scored CVEs.
What is the CVSS score of CVE-2025-69277?
CVE-2025-69277 has a CVSS v3 base score of 4.5 (NVD).
How do I remediate CVE-2025-69277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69277, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69277

Explore →

Is Your Infrastructure Affected by CVE-2025-69277?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs