VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libucl: vulnerability history, versions and safety

libucl is a package in the OSS-Fuzz ecosystem. Vulert records 22 vulnerabilities for it across 4 releases, from Sep 2021 to Jan 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
22 vulnerabilities recorded H3 M16 U3
i
18 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 libucl vulnerabilities

Vulert verdict on libucl i

Updated on 23 Oct 2026

Careful: 18 of the 22 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 22 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 18 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 22 over 2 years · 0 in the last year i
  • Latest disclosure 19 Jan 2024 i
  • Highest CVSS n/a i
  • With no published fix 18 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 libucl, 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
0.9.2 H1 M4 No Details →
0.9.1 H1 M4 No Details →
0.9.0 H1 M4 No Details →
0.8.2 H2 M4 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 5
  • 2022 6
  • 2023 10
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for libucl

The 5 most severe of 22 vulnerabilities recorded for this package

Search all 22 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in libucl: ucl_object_dtor_unref_single N/A medium No fix published 18 Feb 2023
Heap-use-after-free vulnerability in libucl N/A high c8374381bab04f33f0000910acdf37593e343c99 17 Apr 2023
Heap-use-after-free vulnerability in libucl N/A high 5c58d0d5b939daf6f0c389e15019319f138636c2 19 Jan 2024
Heap-buffer-overflow in libucl: ucl_object_dtor_unref_single N/A medium No fix published 07 Dec 2022
UNKNOWN READ vulnerability in libucl N/A medium No fix published 11 Dec 2021

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 libucl

Is libucl safe to use?

Vulert records 22 vulnerabilities for libucl in OSS-Fuzz: 0 critical, 3 high, 16 medium and 0 low, plus 3 not yet rated. 18 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libucl have?

22 vulnerabilities are recorded for libucl in the OSS-Fuzz ecosystem: 0 critical, 3 high, 16 medium and 0 low, plus 3 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 libucl vulnerabilities disclosed?

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

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