VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

poco: vulnerability history, versions and safety

poco is a package in the Debian ecosystem. Vulert records 11 vulnerabilities for it across 18 releases, from Apr 2014 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded U11
i
4 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 poco vulnerabilities

Vulert verdict on poco i

Updated on 23 Oct 2026

Careful: 4 of the 11 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

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

What to do: Plan around the 4 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 11 over 11 years · 0 in the last year i
  • Latest disclosure 06 Aug 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 4 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 poco, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2018 2
  • 2024 2
  • 2025 5

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

03 Vulnerabilities

Recorded vulnerabilities for poco

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Integer Overflow and Buffer Overflow in POCO Package 9.8 critical 1.10.0-6+deb11u2 27 Jan 2024
Path Traversal Vulnerability in POCO C++ Libraries - CVE-2017-1000472 6.5 medium 1.8.0-2 03 Jan 2018
Vulnerability in Poco Library Allows SSL Server Spoofing N/A unrated 1.3.6p1-5 26 Apr 2014
Critical Security Update for Poco Package: Addressing CVE-2023-52389 N/A unrated 1.10.0-6+deb11u2 20 Jan 2025
Null Pointer Dereference Vulnerability in Poco Package (CVE-2025-6375) N/A unrated No fix published 21 Jun 2025

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 poco

Is poco safe to use?

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

How many vulnerabilities does poco have?

11 vulnerabilities are recorded for poco in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 11 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 poco vulnerabilities disclosed?

0 vulnerabilities were recorded for poco in the last 12 months, and the oldest entry in this database dates to 26 Apr 2014. 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 poco 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 poco for upcoming vulnerabilities?

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