CVE-2025-59391 is an out-of-bounds read (CWE-125) in libcoap's OSCORE configuration-file parser: a boolean configuration value longer than the fixed strings "true" or "false" makes an internal memcmp() comparison read past those string constants in the library's .rodata section, which can crash an application calling coap_new_oscore_conf() or leak the bytes stored next to that string to whoever supplies the configuration file, and NVD has not, as of 2026-11-07, published its own CVSS score for the issue.
Vulnerability summary
CVSS base score
N/A
No NVD score published as of
EPSS score (FIRST)
0.3%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2025-59391 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| obgm/libcoap OSCORE configuration-file parser (open-source C implementation of the CoAP protocol, RFC 7252, embedded in resource-constrained IoT and firmware stacks) | — | Versions before release-4.3.5-patches (fixed in v4.3.5a) |
What does this mean for affected devices?
CVE-2025-59391 (CWE-125, out-of-bounds read) affects the OSCORE (Object Security for Constrained RESTful Environments) configuration-file parser in libcoap, the obgm/libcoap open-source C implementation of CoAP used in resource-constrained IoT and firmware stacks. NVD's description states: "A memory disclosure vulnerability exists in libcoap's OSCORE configuration parser in libcoap before release-4.3.5-patches. An out-of-bounds read may occur when parsing certain configuration values, allowing an attacker to infer or read memory beyond string boundaries in the .rodata section. This could potentially lead to information disclosure or denial of service" (NVD).
The upstream fix, libcoap pull request #1730 ("OSCORE: Fix OSCORE configuration file parsing issue"), explains the mechanics precisely: "With a large boolean parameter value, (longer than 'false'), memory would be read past the 'true' or 'false' string boundaries in the '.rodata' section when doing a memcmp(), potentially causing the application to crash when calling coap_new_oscore_conf() with a specially crafted configuration file. It also can provide a mechanism to determine the byte values following the 'true' or 'false' string boundaries which could lead to accessing sensitive information." The same pull request notes that exploitation "can only be done by a specially crafted local application," since the standard libcoap library itself does not define any keys or certificates to leak, and credits the discovery to SecMate; the fix shipped in release v4.3.5a (libcoap pull request #1730).
NVD lists CVE-2025-59391 with status "Analyzed," but the only severity score on record is a Secondary CVSS v3.1 base score of 6.5 (medium), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L, submitted by CISA's ADP (Authorized Data Publisher) container rather than NVD's own analysts — NVD itself has not published a Primary rating for this CVE, so this page does not present a headline severity figure as NVD-confirmed (NVD).
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog as of catalog version 2026.11.06, and FIRST scores the probability of exploitation at 0.00261 (17.87th percentile) as of 2026-11-06 (CISA KEV, FIRST EPSS).
NVD has not finished its own severity analysis. In the meantime, any firmware or application that parses untrusted OSCORE configuration files with libcoap before release-4.3.5-patches should update to v4.3.5a or later, and should avoid accepting OSCORE configuration data from sources that are not fully trusted.
Evidence
- libcoap's OSCORE configuration parser (before release-4.3.5-patches) can read memory out of bounds past the 'true'/'false' string constants in .rodata when parsing a boolean configuration value, potentially causing a crash or information disclosure. — NVD
- The bug is in a memcmp() comparison inside coap_new_oscore_conf() that does not bound the comparison to the length of the literal 'true'/'false' strings; exploitation requires a specially crafted local application supplying the configuration file; discovered by SecMate; fixed in v4.3.5a. — libcoap pull request #1730
- NVD status is 'Analyzed' but the only recorded score is a Secondary CVSS v3.1 base score of 6.5, submitted by the CISA-ADP source container, not an NVD Primary rating. — NVD
- Not present in the CISA KEV catalog as of catalog version 2026.11.06; EPSS score is 0.00261 (17.87th percentile) as of 2026-11-06. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
What is CVE-2025-59391?
CVE-2025-59391 is an out-of-bounds read (CWE-125) in libcoap's OSCORE configuration-file parser: a boolean configuration value longer than the fixed strings "true" or "false" makes an internal memcmp() comparison read past those string constants in the library's .rodata section, which can crash an application calling coap_new_oscore_conf() or leak the bytes stored next to that string to whoever supplies the configuration file, and NVD has not, as of 2026-11-07, published its own CVSS score for the issue.
How severe is CVE-2025-59391?
CVE-2025-59391 has no NVD CVSS score published as of 2026-11-10, so this page gives it no severity rating rather than assuming low or high risk.
Is CVE-2025-59391 being actively exploited?
CVE-2025-59391 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. FIRST's EPSS model puts its probability of exploitation at 0.26%.
What is affected by CVE-2025-59391?
CVE-2025-59391 affects obgm/libcoap OSCORE configuration-file parser (open-source C implementation of the CoAP protocol, RFC 7252, embedded in resource-constrained IoT and firmware stacks).
Where does this CVE-2025-59391 information come from?
This advisory is based on NVD, libcoap pull request #1730, CISA KEV, and FIRST EPSS, cited in full in the Sources section above.
Questions about this page?