Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2025-69277: libsodium before ad3004e, in atypical use cases involving certain custom cryptography or untrusted data to crypto_core_ed25519_is_valid_poin

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: libsodium libsodium ad3004ec8731730e93fcfbbc824e67eadc1c1bae; azl3 libsodium 1.0.19-1 on Azure Linux 3.0 1.0.19-2; azl3 libsodium 1.0.19-2 on Azure Linux 3.0 1.0.19-2.

Low priority for now. Upgrade to libsodium libsodium ad3004ec8731730e93fcfbbc824e67eadc1c1bae; azl3 libsodium 1.0.19-1 on Azure Linux 3.0 1.0.19-2; azl3 libsodium 1.0.19-2 on Azure Linux 3.0 1.0.19-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.5 · v3.1—No exploit Fix available
Published
Dec 31, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mitre
4.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-69277

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for libsodium records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • libsodium libsodium

    • before ad3004ec8731730e93fcfbbc824e67eadc1c1baeaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.20libsodiumbefore 1.0.19-r11.0.19-r1
Alpine:v3.21libsodiumbefore 1.0.20-r11.0.20-r1
Alpine:v3.23py3-pynaclbefore 1.6.2-r01.6.2-r0
Debian:11libsodiumbefore 1.0.18-1+deb11u11.0.18-1+deb11u1
Debian:12libsodiumbefore 1.0.18-1+deb12u11.0.18-1+deb12u1
Debian:13libsodiumbefore 1.0.18-1+deb13u11.0.18-1+deb13u1
Debian:14libsodiumbefore 1.0.18-21.0.18-2
openSUSE:Leap 15.6libsodiumbefore 1.0.18-150000.4.14.11.0.18-150000.4.14.1
openSUSE:Tumbleweedpython-PyNaClbefore 1.6.2-1.11.6.2-1.1
Packagistparagonie/sodium_compatfrom 2 · before 2.5.02.5.0
Packagistparagonie/sodium_compatbefore 1.24.01.24.0
PyPIhdwalletbefore 3.6.13.6.1
PyPIpynaclbefore 1.6.21.6.2
Red Hat:hummingbird:1libsodiumbefore 0:1.0.22-1.hum10:1.0.22-1.hum1
Red Hat:hummingbird:1libsodium-develbefore 0:1.0.22-1.hum10:1.0.22-1.hum1
Red Hat:hummingbird:1libsodium-staticbefore 0:1.0.22-1.hum10:1.0.22-1.hum1
Red Hat:hummingbird:1mingw32-libsodiumbefore 0:1.0.22-1.hum10:1.0.22-1.hum1
Red Hat:hummingbird:1mingw64-libsodiumbefore 0:1.0.22-1.hum10:1.0.22-1.hum1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSdnsdistbefore 1.8.0-150400.9.8.11.8.0-150400.9.8.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSusbguardbefore 1.1.2-150400.3.5.11.1.2-150400.3.5.1
SUSE:Linux Enterprise Micro 5.3libsodiumbefore 1.0.18-150000.4.14.11.0.18-150000.4.14.1
SUSE:Linux Enterprise Micro 5.3libsodiumbefore 1.0.22-150000.4.17.11.0.22-150000.4.17.1
SUSE:Linux Enterprise Micro 5.3zeromqbefore 4.2.3-150000.3.17.14.2.3-150000.3.17.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7dnsdistbefore 1.9.12-150700.3.11.21.9.12-150700.3.11.2

+11

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
libsodium libsodiumad3004ec8731730e93fcfbbc824e67eadc1c1baeVendor (CNA)
azl3 libsodium 1.0.19-1 on Azure Linux 3.01.0.19-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 libsodium 1.0.19-2 on Azure Linux 3.01.0.19-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libsodium 1.0.18-6 on CBL Mariner 2.01.0.18-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libsodium 1.0.18-7 on CBL Mariner 2.01.0.18-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:libsodium1.0.19-r1 · Alpine:v3.20Package registry (OSV)
alpine:py3-pynacl1.6.2-r0 · Alpine:v3.23Package registry (OSV)
debian:libsodium1.0.18-1+deb12u1 · Debian:12Package registry (OSV)
opensuse:libsodium1.0.18-150000.4.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python-PyNaCl1.6.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
Packagist:paragonie/sodium_compat1.24.0Package registry (OSV)
Packagist:paragonie/sodium_compat2.5.0Package registry (OSV)
PyPI:hdwallet3.6.1Package registry (OSV)
PyPI:pynacl1.6.2Package registry (OSV)
red hat:libsodium0:1.0.22-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:libsodium-devel0:1.0.22-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:libsodium-static0:1.0.22-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:mingw32-libsodium0:1.0.22-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:mingw64-libsodium0:1.0.22-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:apache2-mod_php77.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Legacy 15 SP7Package registry (OSV)
suse:dnsdist1.9.12-150700.3.11.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:libsodium1.0.18-150000.4.14.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:php77.4.33-150400.4.75.2 · SUSE:Linux Enterprise Module for Legacy 15 SP7Package registry (OSV)
suse:php7-embed7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:php7-fastcgi7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:php7-fpm7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:php7-test7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:unbound1.25.2-150600.23.21.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:usbguard1.1.2-150500.6.2.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:zeromq4.2.3-150000.3.17.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-184 · Incomplete List of Disallowed Inputs

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records