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.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the TSSA-2026:0004 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    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.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 42 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2026-b7217393db advisory.

    **Version 1.0.21**

     This point release includes all the changes from 1.0.20-stable, which     include a security fix for the `crypto_core_ed25519_is_valid_point()`     function, as well as two new sets of functions:

     - The new `crypto_ipcrypt_*` functions implement mechanisms for securely     encrypting and anonymizing IP addresses as specified in https://ipcrypt-std.github.io
     - The `sodium_bin2ip` and `sodium_ip2bin` helper functions have been added     to complement the `crypto_ipcrypt_*` functions and easily convert addresses     between bytes and strings.
     - XOF: the `crypto_xof_shake*` and `crypto_xof_turboshake*` functions     are standard extendable output functions. From input of any length, they can     derive output of any length with the same properties as hash functions. These     primitives are required by many post-quantum mechanisms, but can also be used     for a wide range of applications, including key derivation, session encryption     and more.

    ----

    **Version 1.0.20-stable**

     - XCFramework: cross-compilation is now forced on Apple Silicon to     avoid Rosetta-related build issues
     - The Fil-C compiler is supported out of the box
     - The CompCert compiler is supported out of the box
     - MSVC 2026 (Visual Studio 2026) is now supported
     - Zig builds now support FreeBSD targets
     - Performance of AES256-GCM and AEGIS on ARM has been improved     with some compilers
     - Android binaries have been added to the NuGet package
     - Windows ARM binaries have been added to the NuGet package
     - The Android build script has been improved. The base SDK is     now 27c, and the default platform is 21, supporting 16 KB page sizes.
     - The library can now be compiled with Zig 0.15 and Zig 0.16
     - Zig builds now generate position-independent static libraries by     default on targets that support PIC
     - arm64e builds have been added to the XCFramework packages
     - XCFramework packages are now full builds instead of minimal     builds
     - MSVC builds have been enabled for ARM64
     - iOS 32-bit (armv7/armv7s) support has been removed from the     XCFramework build script
     - Security: optblockers have been introduced in critical code paths     to prevent compilers from introducing unwanted side channels via     conditional jumps. This was observed on RISC-V targets with specific     compilers and options.
     - Security: `crypto_core_ed25519_is_valid_point()` now properly     rejects small-order points that are not in the main subgroup
     - `((nonnull))` attributes have been relaxed on some `crypto_stream*`     functions to allow NULL output buffers when the output length is zero
     - A cross-compilation issue with old clang versions has been     fixed
     - JavaScript: support for Cloudflare Workers has been added
     - JavaScript: WASM_BIGINT is forcibly disabled to retain     compatibility with older runtimes
     - A compilation issue with old toolchains on Solaris has been     fixed
     - `crypto_aead_aes256gcm_is_available` is exported to JavaScript
     - libsodium is now compatible with Emscripten 4.x
     - Security: memory fences have been added after MAC verification in     AEAD to prevent speculative access to plaintext before authentication     is complete
     - Assembly files now include .gnu.property notes for proper IBT and     Shadow Stack support when building with CET instrumentation


Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 43 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2026-cb424f8aa2 advisory.

    **Version 1.0.21**

     This point release includes all the changes from 1.0.20-stable, which     include a security fix for the `crypto_core_ed25519_is_valid_point()`     function, as well as two new sets of functions:

     - The new `crypto_ipcrypt_*` functions implement mechanisms for securely     encrypting and anonymizing IP addresses as specified in https://ipcrypt-std.github.io
     - The `sodium_bin2ip` and `sodium_ip2bin` helper functions have been added     to complement the `crypto_ipcrypt_*` functions and easily convert addresses     between bytes and strings.
     - XOF: the `crypto_xof_shake*` and `crypto_xof_turboshake*` functions     are standard extendable output functions. From input of any length, they can     derive output of any length with the same properties as hash functions. These     primitives are required by many post-quantum mechanisms, but can also be used     for a wide range of applications, including key derivation, session encryption     and more.

    ----

    **Version 1.0.20-stable**

     - XCFramework: cross-compilation is now forced on Apple Silicon to     avoid Rosetta-related build issues
     - The Fil-C compiler is supported out of the box
     - The CompCert compiler is supported out of the box
     - MSVC 2026 (Visual Studio 2026) is now supported
     - Zig builds now support FreeBSD targets
     - Performance of AES256-GCM and AEGIS on ARM has been improved     with some compilers
     - Android binaries have been added to the NuGet package
     - Windows ARM binaries have been added to the NuGet package
     - The Android build script has been improved. The base SDK is     now 27c, and the default platform is 21, supporting 16 KB page sizes.
     - The library can now be compiled with Zig 0.15 and Zig 0.16
     - Zig builds now generate position-independent static libraries by     default on targets that support PIC
     - arm64e builds have been added to the XCFramework packages
     - XCFramework packages are now full builds instead of minimal     builds
     - MSVC builds have been enabled for ARM64
     - iOS 32-bit (armv7/armv7s) support has been removed from the     XCFramework build script
     - Security: optblockers have been introduced in critical code paths     to prevent compilers from introducing unwanted side channels via     conditional jumps. This was observed on RISC-V targets with specific     compilers and options.
     - Security: `crypto_core_ed25519_is_valid_point()` now properly     rejects small-order points that are not in the main subgroup
     - `((nonnull))` attributes have been relaxed on some `crypto_stream*`     functions to allow NULL output buffers when the output length is zero
     - A cross-compilation issue with old clang versions has been     fixed
     - JavaScript: support for Cloudflare Workers has been added
     - JavaScript: WASM_BIGINT is forcibly disabled to retain     compatibility with older runtimes
     - A compilation issue with old toolchains on Solaris has been     fixed
     - `crypto_aead_aes256gcm_is_available` is exported to JavaScript
     - libsodium is now compatible with Emscripten 4.x
     - Security: memory fences have been added after MAC verification in     AEAD to prevent speculative access to plaintext before authentication     is complete
     - Assembly files now include .gnu.property notes for proper IBT and     Shadow Stack support when building with CET instrumentation



Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Ubuntu 22.04 LTS / 24.04 LTS / 25.04 / 25.10 host has packages installed that are affected by a vulnerability as referenced in the USN-7949-1 advisory.

    It was discovered that Sodium incorrectly handled the elliptic curve point validity check in certain     atypical use cases. This could result in invalid points being used, contrary to expectations.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 583b63f5-ebae-11f0-939f-47e3830276dd advisory.

    Libsodium maintainer reports:
    The function crypto_core_ed25519_is_valid_point(), a low-level function               used to check if a given elliptic curve point is valid, was supposed to               reject points that aren't in the main cryptographic group,               but some points were slipping through.

Tenable has extracted the preceding description block directly from the FreeBSD security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Debian 11 host has packages installed that are affected by a vulnerability as referenced in the dla-4435 advisory.

    - -----------------------------------------------------------------------     Debian LTS Advisory DLA-4435-1              debian-lts@lists.debian.org     https://www.debian.org/lts/security/                      Utkarsh Gupta     January 07, 2026                            https://wiki.debian.org/LTS
    - -----------------------------------------------------------------------

    Package        : libsodium     Version        : 1.0.18-1+deb11u1     CVE ID         : CVE-2025-69277     Debian Bug     : 1124374

    It was discovered that the crypto_core_ed25519_is_valid_point()     function of the Sodium cryptography library mishandled checks for     valid elliptic curve points.

    For Debian 11 bullseye, this problem has been fixed in version     1.0.18-1+deb11u1.

    We recommend that you upgrade your libsodium packages.

    For the detailed security status of libsodium please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/libsodium

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of libsodium installed on the remote host is prior to 1.0.18 / 1.0.21. It is, therefore, affected by a vulnerability as referenced in the SSA:2026-006-01 advisory.

    New libsodium packages are available for Slackware 15.0 and -current to fix a security issue.

Tenable has extracted the preceding description block directly from the libsodium security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Debian 12 / 13 host has packages installed that are affected by a vulnerability as referenced in the dsa-6094 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6094-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     January 05, 2026                      https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : libsodium     CVE ID         : CVE-2025-69277

    It was discovered that the crypto_core_ed25519_is_valid_point() function     of the Sodium cryptography library mishandled checks for valid elliptic     curve points.

    For the oldstable distribution (bookworm), this problem has been fixed     in version 1.0.18-1+deb12u1.

    For the stable distribution (trixie), this problem has been fixed in     version 1.0.18-1+deb13u1.

    We recommend that you upgrade your libsodium packages.

    For the detailed security status of libsodium please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/libsodium

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2025-69277)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
282607	TencentOS Server 4: libsodium (TSSA-2026:0004)	Nessus	Tencent Local Security Checks	medium
282563	Fedora 42 : libsodium (2026-b7217393db)	Nessus	Fedora Local Security Checks	medium
282549	Fedora 43 : libsodium (2026-cb424f8aa2)	Nessus	Fedora Local Security Checks	medium
282533	Ubuntu 22.04 LTS / 24.04 LTS / 25.04 / 25.10 : Sodium vulnerability (USN-7949-1)	Nessus	Ubuntu Local Security Checks	medium
282453	FreeBSD : security/libsodium -- crypto_core_ed25519_is_valid_point mishandles checks for whether an elliptic curve point is valid (583b63f5-ebae-11f0-939f-47e3830276dd)	Nessus	FreeBSD Local Security Checks	medium
282343	Debian dla-4435 : libsodium-dev - security update	Nessus	Debian Local Security Checks	medium
281901	Slackware Linux 15.0 / current libsodium Vulnerability (SSA:2026-006-01)	Nessus	Slackware Local Security Checks	medium
281783	Debian dsa-6094 : libsodium-dev - security update	Nessus	Debian Local Security Checks	medium
281493	Linux Distros Unpatched Vulnerability : CVE-2025-69277	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-69277

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium