CVE-2025-69277: libsodium has Incomplete List of Disallowed Inputs

Published Dec 31, 2025
·
Updated

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

Other sources

libsodium has Incomplete List of Disallowed Inputs

— Packagist

Affected Software

22 affected componentsFixes available
libsodium<ad3004e
Microsoft azl3 libsodium 1.0.19-1
Microsoft cbl2 libsodium 1.0.18-6
pip/hdwallet<3.6.1
3.6.1
pip/pynacl<1.6.2
1.6.2
composer/paragonie/sodium_compat<1.24.0
1.24.0
composer/paragonie/sodium_compat>=2<2.5.0
2.5.0
Microsoft cbl2 libsodium 1.0.18-7
Patch available
Microsoft azl3 libsodium 1.0.19-1
Patch available
Microsoft azl3 libsodium 1.0.19-2
Patch available
Microsoft cbl2 libsodium 1.0.18-6
Patch available
IBM QRadar<=7.6.0.0 - 7.6.0.4
IBM QRadar<=7.5.0 - 7.5.0 UP16 IF01
composer/paragonie/sodium_compat<1.24.0
1.24.0
composer/paragonie/sodium_compat>=2, <2.5.0
2.5.0
alpine/libsodium<1.0.19-r1
1.0.19-r1
alpine/libsodium<1.0.20-r1
1.0.20-r1
alpine/libsodium<1.0.20-r1
1.0.20-r1
alpine/libsodium<1.0.20-r1
1.0.20-r1
alpine/libsodium<1.0.20-r1
1.0.20-r1
alpine/py3-pynacl<1.6.2-r0
1.6.2-r0
alpine/py3-pynacl<1.6.2-r0
1.6.2-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/hdwallet to a version that resolves this vulnerability.

    Fixed in 3.6.1
  2. Upgrade

    Upgrade pip/PyNaCl to a version that resolves this vulnerability.

    Fixed in 1.6.2
  3. Upgrade

    Upgrade composer/paragonie/sodium_compat to a version that resolves this vulnerability.

    Fixed in 1.24.0
  4. Upgrade

    Upgrade composer/paragonie/sodium_compat to a version that resolves this vulnerability.

    Fixed in 2.5.0
  5. Upgrade

    Upgrade alpine/libsodium to a version that resolves this vulnerability.

    Fixed in 1.0.19-r1
  6. Upgrade

    Upgrade alpine/libsodium to a version that resolves this vulnerability.

    Fixed in 1.0.20-r1
  7. Upgrade

    Upgrade alpine/py3-pynacl to a version that resolves this vulnerability.

    Fixed in 1.6.2-r0

Event History

Dec 31, 2025
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 AM
DescriptionSeverityWeakness
Data Sourced
via OSV·06:15 AM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·06:30 AM
Data Sourced
via GitHub·06:30 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Packagist·06:30 AM
DescriptionSeverityAffected Software
Jan 3, 2026
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeaknessAffected Software
Oct 13, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2025-69277?

CVE-2025-69277 is classified as a high severity vulnerability due to its potential impact on cryptographic operations and data integrity.

2

How do I fix CVE-2025-69277?

To fix CVE-2025-69277, you should upgrade libsodium to a version that is greater than ad3004e to ensure that elliptic curve point validation is handled correctly.

3

What are the potential consequences of CVE-2025-69277?

The consequences of CVE-2025-69277 include the possibility of accepting invalid elliptic curve points, which could lead to unauthorized access or data breaches.

4

What versions of libsodium are affected by CVE-2025-69277?

CVE-2025-69277 affects all versions of libsodium prior to ad3004e.

5

Who is at risk from CVE-2025-69277?

Developers and organizations using affected versions of libsodium for cryptographic operations are at risk from CVE-2025-69277.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203