VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libcoap2: vulnerability history, versions and safety

libcoap2 is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 1 release, from Nov -0001 to Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
i
10 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libcoap2 vulnerabilities

Vulert verdict on libcoap2 i

Updated on 23 Oct 2026

Careful: 10 of the 10 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 10 vulnerabilities on record across 2024 years, none in the last year.

What to do: Plan around the 10 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 2024 years · 0 in the last year i
  • Latest disclosure 09 Oct 2024 i
  • Highest CVSS n/a i
  • With no published fix 10 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libcoap2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.2.1-1 U10 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 9
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libcoap2

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
NULL Pointer Dereference Vulnerability in libcoap Packages N/A unrated No fix published 09 Oct 2024
Critical Vulnerability in libcoap Packages: CVE-2025-65493 N/A unrated No fix published 30 Nov -0001
Critical Vulnerability in libcoap Packages: CVE-2025-65494 N/A unrated No fix published 30 Nov -0001
Critical Vulnerability in libcoap Packages: CVE-2025-65495 N/A unrated No fix published 30 Nov -0001
Critical Vulnerability in libcoap Packages: CVE-2025-65496 N/A unrated No fix published 30 Nov -0001

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libcoap2

Is libcoap2 safe to use?

Vulert records 10 vulnerabilities for libcoap2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libcoap2 have?

10 vulnerabilities are recorded for libcoap2 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libcoap2 vulnerabilities disclosed?

0 vulnerabilities were recorded for libcoap2 in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libcoap2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libcoap2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libcoap2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.