CVE-2025-65494: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2025-65494, organizations should prioritize updating libcoap to a patched version once it becomes available from the maintainers. In the interim, applying custom patches or workarounds to add NULL checks after sk_GENERAL_NAME_value() calls can prevent crashes. Network-level mitigations include filtering and validating incoming certificates to block malformed or suspicious X.509 certificates before they reach vulnerable devices. Implementing strict certificate validation policies and using certificate pinning where feasible can reduce exposure. Monitoring logs and network traffic for unusual certificate-related errors or crashes can help detect exploitation attempts early. For critical deployments, consider isolating vulnerable devices from untrusted networks and employing intrusion detection systems tuned for CoAP anomalies. Vendors and integrators should review their firmware and software supply chains to ensure updated libcoap versions are deployed promptly. Finally, raising awareness among IoT device operators about this vulnerability will facilitate faster response and remediation.
Description
CVE-2025-65494 is a high-severity vulnerability in libcoap 4.3.5, where a NULL pointer dereference occurs in the get_san_or_cn_from_cert() function when processing crafted X.509 certificates. This flaw allows remote attackers to cause a denial of service (DoS) without requiring authentication or user interaction. The vulnerability arises because sk_GENERAL_NAME_value() can return NULL, which is not properly handled, leading to a crash. There are no known exploits in the wild yet, but the CVSS score of 7.5 indicates a significant risk. European organizations using libcoap in IoT or constrained device environments should be particularly vigilant. Mitigation involves applying patches once available and implementing strict certificate validation and input sanitization.