Quick answers
- Is CVE-2025-34468 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-34468 being exploited in the wild.
- How severe is CVE-2025-34468?
- Critical severity, with a CVSS score of 9.8, published 31 December 2025.
- Which products and versions are affected?
- obgm libcoap <= 4.3.5.
- Is there a fix for CVE-2025-34468?
- A patch was published on 2025-09-12: Fix merged into develop branch via commit 30db3ea Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-34468 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-34468?
- Check whether you run Libcoap. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow exists in libcoap's address resolution logic, specifically within the coap_resolve_address_info and coap_split_uri functions. The vulnerability occurs when attacker-controlled hostname data exceeding 255 bytes is copied into a fixed 256-byte stack buffer without adequate bounds checking. A remote, unauthenticated attacker can trigger this overflow if the application has proxy logic enabled. Successful exploitation can lead to a crash (DoS) or remote code execution (RCE), though RCE feasibility depends on local compiler mitigations and memory protections. The issue is addressed in commit 30db3ea and released in version 4.3.5a.
Affected products
- obgm libcoap <= 4.3.5
Timeline
- 2025-09-12: patched: Fix merged into develop branch via commit 30db3ea
- 2025-12-31: disclosed: CVE-2025-34468 published