VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libecc: vulnerability history, versions and safety

libecc is a package in the OSS-Fuzz ecosystem. Vulert records 2 vulnerabilities for it across 2 affected ranges, from May 2021 to Nov 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
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 libecc vulnerabilities

Vulert verdict on libecc i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 2 years, 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 2 over 2 years · 0 in the last year i
  • Latest disclosure 05 Nov 2023 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from b9329e2826f4d622dbb9ffdd9316e98fda7a023f up to b9329e2826f4d622dbb9ffdd9316e98fda7a023f (exclusive) 1
from f3abf297e84874278129fb91bc1b89356dd66627 up to d6cbbbb0c4afb6097dfea9eadf1516759dd337eb (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for libecc

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-of-uninitialized-value in nn_check_initialized in libecc N/A medium d6cbbbb0c4afb6097dfea9eadf1516759dd337eb 12 May 2021
Use-of-uninitialized-value in libecc: fp_uninit N/A medium b9329e2826f4d622dbb9ffdd9316e98fda7a023f 05 Nov 2023

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 libecc

Is libecc safe to use?

Vulert records 2 vulnerabilities for libecc in OSS-Fuzz: 0 critical, 0 high, 2 medium and 0 low. 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 libecc have?

2 vulnerabilities are recorded for libecc in the OSS-Fuzz ecosystem: 0 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libecc vulnerabilities disclosed?

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

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