Vulnerability Database · OSS-Fuzz · Package report

llamacpp: vulnerability history, versions and safety

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

i
4 vulnerabilities recorded M3 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.

Vulert verdict on llamacpp i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 4 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 4 over 1 year · 0 in the last year i
  • Latest disclosure 03 Nov 2024 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 llamacpp, 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
b4002 M2 U1 Yes Details →
b4001 M2 U1 Yes Details →
b4000 M2 U1 Yes Details →
b3999 M2 U1 Yes Details →
b3998 M2 U1 Yes Details →
b3997 M2 U1 Yes Details →
b3996 M2 U1 Yes Details →
b3995 M2 U1 Yes Details →
b3994 M2 U1 Yes Details →
b3991 M2 U1 Yes Details →
b3990 M2 U1 Yes Details →
b3989 M3 U1 Yes Details →
b3988 M3 U1 Yes Details →
b3987 M2 Yes Details →
b3985 M2 Yes Details →
b3984 M2 Yes Details →
b3983 M2 Yes Details →
b3982 M2 Yes Details →
b3978 M2 Yes Details →
b3977 M2 Yes Details →
b3976 M2 Yes Details →
b3975 M2 Yes Details →
b3974 M2 Yes Details →
b3972 M2 Yes Details →
b3971 M2 Yes Details →
b3970 M2 Yes Details →
b3969 M2 Yes Details →
b3967 M2 Yes Details →
b3965 M2 Yes Details →
b3964 M2 Yes Details →
b3962 M2 Yes Details →
b3961 M2 Yes Details →
b3960 M2 Yes Details →
b3959 M2 Yes Details →
b3958 M2 Yes Details →
b3957 M2 Yes Details →
b3952 M2 Yes Details →
b3950 M2 Yes Details →
b3949 M2 Yes Details →
b3948 M2 Yes Details →
b3947 M2 Yes Details →
b3946 M2 Yes Details →
b3943 M2 Yes Details →
b3942 M2 Yes Details →
b3941 M2 Yes Details →
b3940 M2 Yes Details →
b3939 M2 Yes Details →
b3938 M2 Yes Details →
b3937 M2 Yes Details →
b3936 M2 Yes Details →
b3935 M2 Yes Details →
b3933 M2 Yes Details →
b3932 M2 Yes Details →
b3931 M2 Yes Details →
b3930 M2 Yes Details →
b3928 M2 Yes Details →
b3927 M2 Yes Details →
b3926 M2 Yes Details →
b3925 M2 Yes Details →
b3923 M2 Yes Details →
b3922 M2 Yes Details →
b3921 M2 Yes Details →
b3920 M2 Yes Details →
b3917 M2 Yes Details →
b3916 M2 Yes Details →
b3914 M2 Yes Details →
b3912 M2 Yes Details →
b3911 M2 Yes Details →
b3909 M2 Yes Details →
b3907 M2 Yes Details →
b3906 M2 Yes Details →
b3905 M2 Yes Details →
b3904 M2 Yes Details →
b3903 M2 Yes Details →
b3902 M2 Yes Details →
b3901 M2 Yes Details →
b3899 M2 Yes Details →
b3898 M2 Yes Details →
b3896 M2 Yes Details →
b3895 M2 Yes Details →
b3892 M2 Yes Details →
b3889 M2 Yes Details →
b3887 M2 Yes Details →
b3886 M2 Yes Details →
b3883 M2 Yes Details →
b3880 M2 Yes Details →
b3879 M2 Yes Details →
b3878 M2 Yes Details →
b3874 M2 Yes Details →
b3873 M2 Yes Details →
b3872 M2 Yes Details →
b3870 M2 Yes Details →
b3869 M2 Yes Details →
b3868 M2 Yes Details →
b3867 M2 Yes Details →
b3866 M2 Yes Details →
b3865 M2 Yes Details →
b3864 M2 Yes Details →
b3863 M2 Yes Details →
b3861 M2 Yes Details →
b3856 M2 Yes Details →
b3855 M2 Yes Details →
b3853 M2 Yes Details →
b3849 M2 Yes Details →
b3848 M2 Yes Details →
b3847 M2 Yes Details →
b3841 M2 Yes Details →
b3837 M2 Yes Details →
b3835 M2 Yes Details →
b3834 M2 Yes Details →
b3832 M2 Yes Details →
b3831 M2 Yes Details →
b3829 M2 Yes Details →
b3828 M2 Yes Details →
b3827 M2 Yes Details →
b3825 M2 Yes Details →
b3824 M2 Yes Details →
b3823 M2 Yes Details →
b3822 M2 Yes Details →
b3821 M2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 4

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

03 Vulnerabilities

Recorded vulnerabilities for llamacpp

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
UNKNOWN READ Vulnerability in llamacpp Package N/A medium c5b0f4b5d90297f3e729fca7f78ddb25fcab5ddc 19 Sep 2024
Heap Buffer Overflow Vulnerability in llamacpp Package N/A medium e597e50794f07ec8dc24b9efb18f94ec6386fda0 13 Sep 2024
Segmentation Fault in Llama.cpp: Vulnerability in llama_output_reserve N/A unrated e597e50794f07ec8dc24b9efb18f94ec6386fda0 01 Nov 2024
Memory Safety Issue in llamacpp: UNKNOWN READ Vulnerability N/A medium e597e50794f07ec8dc24b9efb18f94ec6386fda0 03 Nov 2024

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 llamacpp

Is llamacpp safe to use?

Vulert records 4 vulnerabilities for llamacpp in OSS-Fuzz: 0 critical, 0 high, 3 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 llamacpp have?

4 vulnerabilities are recorded for llamacpp in the OSS-Fuzz ecosystem: 0 critical, 0 high, 3 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 llamacpp vulnerabilities disclosed?

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

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