libcoap3: libcoap versions up to and including 4.3.5, prior to commit 30db3ea, contain a stack-based buffer overflow in address...
CVE-2025-34468 is fixed in 8 products on 1 platform, first by DEBIAN-CVE-2025-34468, released December 31, 2025. It is not reported as exploited. Patch Radar priority: Urgent.
libcoap versions up to and including 4.3.5, prior to commit 30db3ea, contain a stack-based buffer overflow in address resolution when attacker-controlled hostname data is copied into a fixed 256-byte stack buffer without proper bounds checking. A remote attacker can trigger a crash and potentially achieve remote code execution depending on compiler options and runtime memory protections. Exploitation requires the proxy logic to be enabled (i.e., the proxy request handling code path in an application using libcoap).
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libcoap · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap-debuginfo · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap-debugsource · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap-devel · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap-doc · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap-utils · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap-utils-debuginfo · Fedora 43 | 4.3.5b-1.fc43 | FEDORA-2026-0CE923A09D | Apr 17, 2026 |
| libcoap3 · Debian 13.5 (trixie) | 4.3.4-1.1+deb13u3 | DEBIAN-CVE-2025-34468 | Dec 31, 2025 |
| libcoap3 · Debian 14 | 4.3.5-3 | DEBIAN-CVE-2025-34468 | Dec 31, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.