How severe is CVE-2026-10512?

CVE-2026-10512 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-10512 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (18th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-10512?

CVE-2026-10512 affects Wolfssl. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-10512?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-10512 have an EU (EUVD) identifier?

Yes. CVE-2026-10512 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39552.

When was CVE-2026-10512 published?

CVE-2026-10512 was published on 2026-06-25 and last updated on 2026-06-26.

CVE-2026-10512

CVE-2026-10512 is a high-severity vulnerability in Wolfssl with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-682.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 2.3
EPSS exploit prediction: 0% (18th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-39552
Weakness: CWE-682
Affected product: Wolfssl
Published: 2026-06-25
Last modified: 2026-06-26

Description

The X25519 x86_64 assembly implementation fails to clear the most significant bit during the final modular reduction, so the computed result may not be fully reduced modulo the field prime 2^255 - 19. This can leave the field element in a non-canonical form, producing an incorrect result from the scalar multiplication and potentially a wrong shared secret. The final carry-propagation chains in the x64 and AVX2 reduction routines could overflow into the top bit, and the high limb was not masked afterward, so the 255-bit field element was left non-canonical.

Frequently asked questions

What is CVE-2026-10512?: The X25519 x86_64 assembly implementation fails to clear the most significant bit during the final modular reduction, so the computed result may not be fully reduced modulo the field prime 2^255 - 19. This can leave the field element in a non-canonical form, producing an incorrect result from the scalar multiplication and potentially a wrong shared secret. The final carry-propagation chains in the x64 and AVX2 reduction routines could overflow into the top bit, and the high limb was not masked afterward, so the 255-bit field element was left non-canonical.
How severe is CVE-2026-10512?: CVE-2026-10512 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-10512 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (18th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-10512?: CVE-2026-10512 affects Wolfssl. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-10512?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-10512 have an EU (EUVD) identifier?: Yes. CVE-2026-10512 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39552.
When was CVE-2026-10512 published?: CVE-2026-10512 was published on 2026-06-25 and last updated on 2026-06-26.

References

Affected products (1)

cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*

More vulnerabilities in Wolfssl

CVE-2026-7531 — Critical (CVSS 9.8): Use-after-free in PQC hybrid key-share handling. This is an incomplete-fix follow-up to CVE-2026-5460 (released in…
CVE-2026-5264 — Critical (CVSS 9.8): Heap buffer overflow in DTLS 1.3 ACK message processing. A remote attacker can send a crafted DTLS 1.3 ACK message that…
CVE-2026-5187 — Critical (CVSS 9.8): Two potential heap out-of-bounds write locations existed in DecodeObjectId() in wolfcrypt/src/asn.c. First, a bounds…
CVE-2026-4395 — Critical (CVSS 9.8): Heap-based buffer overflow in the KCAPI ECC code path of wc_ecc_import_x963_ex() in wolfSSL wolfcrypt allows a remote…
CVE-2026-3849 — Critical (CVSS 9.8): Stack Buffer Overflow in wc_HpkeLabeledExtract via Oversized ECH Config. A vulnerability existed in wolfSSL 5.8.4 ECH…
CVE-2026-3549 — Critical (CVSS 9.8): Heap Overflow in TLS 1.3 ECH parsing. An integer underflow existed in ECH extension parsing logic when calculating a…

All CVEs affecting Wolfssl →

Other CWE-682 vulnerabilities

CVE-2023-2163 — Critical (CVSS 10.0): Incorrect verifier pruning in BPF in Linux Kernel >=5.4 leads to unsafe code paths being incorrectly marked as safe,…
CVE-2026-1229 — Critical (CVSS 9.8): The CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific…
CVE-2024-36736 — Critical (CVSS 9.8): An issue in the oneflow.permute component of OneFlow-Inc. Oneflow v0.9.1 causes an incorrect calculation when the same…
CVE-2022-30600 — Critical (CVSS 9.8): A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout…
CVE-2021-44847 — Critical (CVSS 9.8): A stack-based buffer overflow in handle_request function in DHT.c in toxcore 0.1.9 through 0.1.11 and 0.2.0 through…
CVE-2020-0221 — Critical (CVSS 9.8): Airbrush FW's scratch memory allocator is susceptible to numeric overflow. When the overflow occurs, the next…

Browse all CWE-682 vulnerabilities →