Vulnerability Database · Hex · Package report

livebook: vulnerability history, versions and safety

livebook is a package in the Hex ecosystem. Vulert records 6 vulnerabilities for it across 70 releases, from Jun 2023 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H1 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 05 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on livebook 0.19.10 i

Updated on 23 Oct 2026

Good news: 0.19.10, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 82/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Stay on 0.19.10 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.19.10 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.19.10 — unaffected i
  • Vulnerabilities on record 6 over 3 years · 5 in the last year i
  • Latest disclosure 05 Aug 2026 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 163,544 packages i
  • Last release 1 month ago i

Version list, release dates, licence and dependants published by hex.pm, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for livebook, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.19.10 18 Sep 2026 none — — Details →
0.19.9 05 Aug 2026 none — — Details →
0.19.8 20 May 2026 U5 — Yes Details →
0.19.7 22 Apr 2026 U5 — Yes Details →
0.19.6 27 Mar 2026 U4 — Yes Details →
0.19.5 23 Mar 2026 U4 — Yes Details →
0.19.4 18 Mar 2026 U4 — Yes Details →
0.19.3 10 Mar 2026 U4 — Yes Details →
0.19.2 04 Mar 2026 U4 — Yes Details →
0.19.1 04 Mar 2026 U4 — Yes Details →
0.19.0 03 Mar 2026 U4 — Yes Details →
0.18.7 05 Aug 2026 none — — Details →
0.18.6 19 Feb 2026 U4 — Yes Details →
0.18.5 03 Feb 2026 U4 — Yes Details →
0.18.4 03 Feb 2026 U4 — Yes Details →
0.18.3 14 Jan 2026 U4 — Yes Details →
0.18.2 15 Dec 2025 U4 — Yes Details →
0.18.1 07 Dec 2025 U4 — Yes Details →
0.18.0 01 Dec 2025 U4 — Yes Details →
0.17.3 23 Oct 2025 U4 — Yes Details →
0.17.2 15 Sep 2025 U4 — Yes Details →
0.17.1 04 Sep 2025 U4 — Yes Details →
0.17.0 04 Sep 2025 U4 — Yes Details →
0.16.4 20 Jun 2025 U4 — Yes Details →
0.16.3 17 Jun 2025 U4 — Yes Details →
0.16.2 04 Jun 2025 U4 — Yes Details →
0.16.1 21 May 2025 U4 — Yes Details →
0.16.0 20 May 2025 U4 — Yes Details →
0.15.5 03 Apr 2025 U4 — Yes Details →
0.15.4 12 Mar 2025 U4 — Yes Details →
0.15.3 10 Mar 2025 U4 — Yes Details →
0.15.2 03 Mar 2025 U4 — Yes Details →
0.15.1 24 Feb 2025 U4 — Yes Details →
0.15.0 20 Feb 2025 U4 — Yes Details →
0.14.7 01 Feb 2025 U3 — Yes Details →
0.14.6 23 Jan 2025 U3 — Yes Details →
0.14.5 25 Oct 2024 U3 — Yes Details →
0.14.4 04 Oct 2024 U3 — Yes Details →
0.14.3 03 Oct 2024 U3 — Yes Details →
0.14.2 20 Sep 2024 U3 — Yes Details →
0.14.1 20 Sep 2024 U3 — Yes Details →
0.14.0 26 Aug 2024 U3 — Yes Details →
0.14.0-rc.1 19 Aug 2024 U3 — Yes Details →
0.14.0-rc.0 26 Jul 2024 U3 — Yes Details →
0.13.3 05 Jul 2024 U3 — Yes Details →
0.13.2 26 Jun 2024 U3 — Yes Details →
0.13.1 25 Jun 2024 U3 — Yes Details →
0.13.0 25 Jun 2024 U3 — Yes Details →
0.12.1 25 Dec 2023 U2 — Yes Details →
0.12.0 22 Dec 2023 U2 — Yes Details →
0.11.4 09 Nov 2023 U2 — Yes Details →
0.11.3 25 Oct 2023 U2 — Yes Details →
0.11.2 14 Oct 2023 U2 — Yes Details →
0.11.1 10 Oct 2023 U2 — Yes Details →
0.11.0 09 Oct 2023 U2 — Yes Details →
0.10.0 14 Jul 2023 U1 — Yes Details →
0.9.3 20 Jun 2023 U1 — Yes Details →
0.9.2 14 Apr 2023 U1 — Yes Details →
0.9.1 05 Apr 2023 U1 — Yes Details →
0.9.0 20 Mar 2023 U1 — Yes Details →
0.8.2 20 Jun 2023 U1 — Yes Details →
0.8.1 18 Jan 2023 U1 — Yes Details →
0.8.0 08 Dec 2022 U1 — Yes Details →
0.7.2 26 Oct 2022 U1 — Yes Details →
0.7.1 09 Oct 2022 U1 — Yes Details →
0.7.0 07 Oct 2022 U1 — Yes Details →
0.6.3 13 Jul 2022 U1 — Yes Details →
0.6.2 30 Jun 2022 U1 — Yes Details →
0.6.1 06 May 2022 U1 — Yes Details →
0.6.0 03 May 2022 U1 — Yes Details →
0.5.2 27 Jan 2022 U1 — Yes Details →
0.5.1 20 Jan 2022 U1 — Yes Details →
0.5.0 19 Jan 2022 U1 — Yes Details →
0.4.1 09 Dec 2021 none — — Details →
0.4.0 05 Dec 2021 none — — Details →
0.3.2 10 Nov 2021 none — — Details →
0.3.1 27 Oct 2021 none — — Details →
0.3.0 19 Oct 2021 none — — Details →
0.2.3 12 Aug 2021 none — — Details →
0.2.2 01 Jul 2021 none — — Details →
0.2.1 24 Jun 2021 none — — Details →
0.2.0 17 Jun 2021 none — — Details →
0.1.2 01 Jun 2021 none — — Details →
0.1.1 24 May 2021 none — — Details →
0.1.0 19 May 2021 none — — Details →

All 85 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 5

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

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 livebook

Is livebook safe to use?

Vulert records 6 vulnerabilities for livebook in Hex: 0 critical, 1 high, 0 medium and 0 low, plus 5 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.

What is livebook's Vulert package health score?

Vulert scores livebook 82/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of livebook affected?

No. 0.19.10, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does livebook have?

6 vulnerabilities are recorded for livebook in the Hex ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 5 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 livebook vulnerabilities disclosed?

5 vulnerabilities were recorded for livebook in the last 12 months, and the oldest entry in this database dates to 21 Jun 2023. 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 livebook 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 livebook for upcoming vulnerabilities?

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