VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

poco: vulnerability history, versions and safety

poco is a package in the OSS-Fuzz ecosystem. Vulert records 7 vulnerabilities for it across 2 releases, from Sep 2024 to Apr 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded M6 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 20 Apr 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 7 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 20 Apr 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 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.

i
Version Vulert vulnerabilities Fix published Details
poco-1.14.1-release M4 U1 Yes Details →
poco-1.14.0-release M6 U1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 4
  • 2025 3

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

03 Vulnerabilities

Recorded vulnerabilities for poco

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Segmentation Fault in Poco Package: ios_base Destructor Issue N/A unrated 11619a9e95c2ce14a0edfeddb8c1a0a1c926ba7f 05 Nov 2024
Uninitialized Value Use in Poco Package - OSV-2024-1071 N/A medium bd7be38d6fe7eff50e65223ffe39fb2cbac1c521 15 Sep 2024
Use-of-Uninitialized-Value Vulnerability in Poco Package: NTLMCredentials Parse Challenge Message N/A medium 7297033be78f8fab21cce57fceb445e76bdbee26 13 Oct 2024
Critical UNKNOWN READ Vulnerability in Poco Package: UTF16Encoding::queryConvert N/A medium be2748de0f34f7c48d5055c268bd12ecd32f8dc0 14 Oct 2024
Critical UNKNOWN READ Vulnerability in Poco Package N/A medium be2748de0f34f7c48d5055c268bd12ecd32f8dc0 16 Jan 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 7 vulnerabilities for poco in OSS-Fuzz: 0 critical, 0 high, 6 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does poco have?

7 vulnerabilities are recorded for poco in the OSS-Fuzz ecosystem: 0 critical, 0 high, 6 medium and 0 low, plus 1 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 15 Sep 2024. 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.