VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

llama-cpp-2: vulnerability history, versions and safety

llama-cpp-2 is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io ecosystem.

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 llama-cpp-2 vulnerabilities

Vulert verdict on llama-cpp-2 0.1.160 i

Updated on 23 Oct 2026

Good news: 0.1.160, the version you would install today, has no known vulnerabilities.

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 0.1.160 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 656 i
  • Last release this month i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, 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 llama-cpp-2, 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.1.160 15 Oct 2026 none Apache-2.0 OR MIT — Details →
0.1.159 07 Oct 2026 none Apache-2.0 OR MIT — Details →
0.1.158 30 Sep 2026 none Apache-2.0 OR MIT — Details →
0.1.157 22 Sep 2026 none Apache-2.0 OR MIT — Details →
0.1.156 02 Sep 2026 none Apache-2.0 OR MIT — Details →
0.1.155 31 Aug 2026 none Apache-2.0 OR MIT — Details →
0.1.154 05 Aug 2026 none Apache-2.0 OR MIT — Details →
0.1.153 28 Jul 2026 none Apache-2.0 OR MIT — Details →
0.1.152 21 Jul 2026 none Apache-2.0 OR MIT — Details →
0.1.151 06 Jul 2026 none Apache-2.0 OR MIT — Details →
0.1.150 16 Jun 2026 none Apache-2.0 OR MIT — Details →
0.1.149 16 Jun 2026 none Apache-2.0 OR MIT — Details →
0.1.147 16 Jun 2026 none Apache-2.0 OR MIT — Details →
0.1.146 30 Apr 2026 none Apache-2.0 OR MIT — Details →
0.1.145 22 Apr 2026 none Apache-2.0 OR MIT — Details →
0.1.144 19 Apr 2026 none Apache-2.0 OR MIT — Details →
0.1.143 07 Apr 2026 none Apache-2.0 OR MIT — Details →
0.1.142 06 Apr 2026 none Apache-2.0 OR MIT — Details →
0.1.141 29 Mar 2026 none Apache-2.0 OR MIT — Details →
0.1.140 23 Mar 2026 none Apache-2.0 OR MIT — Details →
0.1.139 17 Mar 2026 none Apache-2.0 OR MIT — Details →
0.1.138 04 Mar 2026 none Apache-2.0 OR MIT — Details →
0.1.137 01 Mar 2026 none Apache-2.0 OR MIT — Details →
0.1.136 23 Feb 2026 none Apache-2.0 OR MIT — Details →
0.1.135 18 Feb 2026 none Apache-2.0 OR MIT — Details →
0.1.134 17 Feb 2026 none Apache-2.0 OR MIT — Details →
0.1.133 03 Feb 2026 none Apache-2.0 OR MIT — Details →
0.1.132 15 Jan 2026 none Apache-2.0 OR MIT — Details →
0.1.131 02 Jan 2026 none Apache-2.0 OR MIT — Details →
0.1.130 13 Dec 2025 none Apache-2.0 OR MIT — Details →
0.1.129 04 Dec 2025 none Apache-2.0 OR MIT — Details →
0.1.128 28 Nov 2025 none Apache-2.0 OR MIT — Details →
0.1.127 26 Nov 2025 none Apache-2.0 OR MIT — Details →
0.1.126 20 Nov 2025 none Apache-2.0 OR MIT — Details →
0.1.125 14 Nov 2025 none Apache-2.0 OR MIT — Details →
0.1.124 05 Nov 2025 none Apache-2.0 OR MIT — Details →
0.1.123 03 Nov 2025 none Apache-2.0 OR MIT — Details →
0.1.122 20 Sep 2025 none Apache-2.0 OR MIT — Details →
0.1.121 05 Sep 2025 none Apache-2.0 OR MIT — Details →
0.1.120 05 Sep 2025 none Apache-2.0 OR MIT — Details →
0.1.119 30 Aug 2025 none Apache-2.0 OR MIT — Details →
0.1.118 18 Aug 2025 none Apache-2.0 OR MIT — Details →
0.1.117 12 Aug 2025 none Apache-2.0 OR MIT — Details →
0.1.116 07 Aug 2025 none Apache-2.0 OR MIT — Details →
0.1.115 07 Aug 2025 none Apache-2.0 OR MIT — Details →
0.1.114 04 Aug 2025 none Apache-2.0 OR MIT — Details →
0.1.113 30 Jul 2025 none Apache-2.0 OR MIT — Details →
0.1.112 26 Jul 2025 none Apache-2.0 OR MIT — Details →
0.1.109 09 Jul 2025 none Apache-2.0 OR MIT — Details →
0.1.108 05 Jun 2025 none Apache-2.0 OR MIT — Details →
0.1.107 26 May 2025 none Apache-2.0 OR MIT — Details →
0.1.103 02 May 2025 none Apache-2.0 OR MIT — Details →
0.1.102 25 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.101 25 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.100 24 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.99 24 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.98 21 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.97 21 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.96 15 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.95 15 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.94 14 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.93 10 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.92 03 Feb 2025 none Apache-2.0 OR MIT — Details →
0.1.91 30 Jan 2025 none Apache-2.0 OR MIT — Details →
0.1.90 27 Jan 2025 none Apache-2.0 OR MIT — Details →
0.1.89 22 Jan 2025 none Apache-2.0 OR MIT — Details →
0.1.88 20 Jan 2025 none Apache-2.0 OR MIT — Details →
0.1.87 15 Jan 2025 none Apache-2.0 OR MIT — Details →
0.1.86 02 Jan 2025 none Apache-2.0 OR MIT — Details →
0.1.85 05 Dec 2024 none Apache-2.0 OR MIT — Details →
0.1.84 27 Nov 2024 none Apache-2.0 OR MIT — Details →
0.1.83 29 Oct 2024 none Apache-2.0 OR MIT — Details →
0.1.82 11 Oct 2024 none Apache-2.0 OR MIT — Details →
0.1.81 08 Oct 2024 none Apache-2.0 OR MIT — Details →
0.1.69 30 Aug 2024 none Apache-2.0 OR MIT — Details →
0.1.68 23 Aug 2024 none Apache-2.0 OR MIT — Details →
0.1.67 21 Aug 2024 none Apache-2.0 OR MIT — Details →
0.1.66 13 Aug 2024 none Apache-2.0 OR MIT — Details →
0.1.65 09 Aug 2024 none Apache-2.0 OR MIT — Details →
0.1.64 26 Jul 2024 none Apache-2.0 OR MIT — Details →
0.1.62 09 Jul 2024 none Apache-2.0 OR MIT — Details →
0.1.60 29 Jun 2024 none Apache-2.0 OR MIT — Details →
0.1.59 29 Jun 2024 none Apache-2.0 OR MIT — Details →
0.1.58 20 Jun 2024 none Apache-2.0 OR MIT — Details →
0.1.57 19 Jun 2024 none Apache-2.0 OR MIT — Details →
0.1.56 14 Jun 2024 none Apache-2.0 OR MIT — Details →
0.1.55 06 Jun 2024 none Apache-2.0 OR MIT — Details →
0.1.54 31 May 2024 none Apache-2.0 OR MIT — Details →
0.1.53 25 May 2024 none Apache-2.0 OR MIT — Details →
0.1.52 08 May 2024 none Apache-2.0 OR MIT — Details →
0.1.51 25 Apr 2024 none Apache-2.0 OR MIT — Details →
0.1.50 21 Apr 2024 none Apache-2.0 OR MIT — Details →
0.1.49 13 Apr 2024 none Apache-2.0 OR MIT — Details →
0.1.48 12 Apr 2024 none Apache-2.0 OR MIT — Details →
0.1.47 06 Apr 2024 none Apache-2.0 OR MIT — Details →
0.1.46 01 Apr 2024 none Apache-2.0 OR MIT — Details →
0.1.45 27 Mar 2024 none Apache-2.0 OR MIT — Details →
0.1.44 25 Mar 2024 none Apache-2.0 OR MIT — Details →
0.1.43 20 Mar 2024 none Apache-2.0 OR MIT — Details →
0.1.42 18 Mar 2024 none Apache-2.0 OR MIT — Details →
0.1.41 14 Mar 2024 none — — Details →
0.1.40 14 Mar 2024 none — — Details →
0.1.39 13 Mar 2024 none — — Details →
0.1.38 11 Mar 2024 none — — Details →
0.1.37 07 Mar 2024 none — — Details →
0.1.36 05 Mar 2024 none — — Details →
0.1.35 05 Mar 2024 none — — Details →
0.1.34 29 Feb 2024 none — — Details →
0.1.33 29 Feb 2024 none — — Details →
0.1.32 27 Feb 2024 none — — Details →
0.1.31 26 Feb 2024 none — — Details →
0.1.30 25 Feb 2024 none — — Details →
0.1.29 25 Feb 2024 none — — Details →
0.1.28 21 Feb 2024 none — — Details →
0.1.27 17 Feb 2024 none — — Details →
0.1.26 12 Feb 2024 none — — Details →
0.1.25 02 Feb 2024 none — — Details →
0.1.22 30 Jan 2024 none — — Details →
0.1.21 27 Jan 2024 none — — Details →
0.1.20 26 Jan 2024 none — — Details →

The newest 120 of 138 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for llama-cpp-2

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 llama-cpp-2

Is llama-cpp-2 safe to use?

Vulert has no vulnerabilities on record for llama-cpp-2 in crates.io at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is llama-cpp-2's Vulert package health score?

Vulert scores llama-cpp-2 85/100, which reads as healthy. 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 llama-cpp-2 affected?

No. 0.1.160, 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 llama-cpp-2 have?

0 vulnerabilities are recorded for llama-cpp-2 in the crates.io ecosystem: 0 critical, 0 high, 0 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 llama-cpp-2 vulnerabilities disclosed?

0 vulnerabilities were recorded for llama-cpp-2 in the last 12 months. 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 llama-cpp-2 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 llama-cpp-2 for upcoming vulnerabilities?

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