CVE-2025-65493

NULL pointer dereference in src/coap_openssl.c in OISM libcoap 4.3.5 allows remote attackers to cause a denial of service via a crafted DTLS/TLS connection that triggers BIO_get_data() to return NULL.

Published: 2025-11-24 Last update: 2025-12-01 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-65493 is rated Moderate Risk (44.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.20%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-65493

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-22 0.29% 0.20% -0.09%
2 2026-03-26 0.18% 0.29% +0.11%
3 2026-01-18 — 0.18% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-65493

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-65493

OS Trackers for CVE-2025-65493

vendor priority summary link
alpine — CVE-2025-65493: 1 source package rows (libcoap); 3 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2025-65493
debian not yet assigned CVE-2025-65493 not yet assigned priority: Debian including 2 source packages (libcoap2, libcoap3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2025-65493
ubuntu medium CVE-2025-65493 medium priority: Ubuntu including 3 source packages (libcoap, libcoap2, libcoap3), 17 status rows across 7 suites (bionic, focal, jammy, noble, plucky, questing, upstream): needs-triage 9, DNE 7, ignored 1. https://ubuntu.com/security/CVE-2025-65493

Affected software / configurations for CVE-2025-65493

Vendor Product Version Raw CPE
libcoap libcoap 4.3.5 cpe:2.3:a:libcoap:libcoap:4.3.5:-:*:*:*:*:*:*

References for CVE-2025-65493

cvelogic Threat Intelligence