CVE-2026-52132: llama.cpp through commit 97f06e9, when started with the --reranking flag, allows remote attackers to cause a d

Q: How do I fix CVE-2026-52132?

llama.cpp: upgrade to newer than 0.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-52132 being exploited?

CVE-2026-52132 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-52132 affect?

CVE-2026-52132 affects llama.cpp. Severity is high (CVSS 7.5). llama.cpp through commit 97f06e9, when started with the --reranking flag, allows remote attackers to cause a denial of service (std::bad_alloc and HTTP 500) via a negative top_n value in a POST request to /rerank.

Q: How urgent is CVE-2026-52132?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2026-52132 is a high-severity flaw (CVSS 7.5) affecting llama.cpp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

llama.cpp through commit 97f06e9, when started with the --reranking flag, allows remote attackers to cause a denial of service (std::bad_alloc and HTTP 500) via a negative top_n value in a POST request to /rerank.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-674
Published	2026-09-01
Last modified	2026-09-04

Publisher (CNA): MITRE · Vendor: ggml

Last updated 2026-09-04 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-01 18:17 UTCPublished CVE record published
2026-09-04 20:15 UTCUpdated Record last modified

ggml llama.cpp UPGRADE

Affected: <= 0.4.0

Fixed in: newer than 0.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy llama.cpp || rpm -q llama.cpp || llama.cpp --version

2. UPGRADE to newer than 0.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade llama.cpp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade llama.cpp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-52132?

llama.cpp: upgrade to newer than 0.4.0. Exact commands for each OS are on this page.

Is CVE-2026-52132 being exploited?

CVE-2026-52132 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-52132 affect?

CVE-2026-52132 affects llama.cpp. Severity is high (CVSS 7.5). llama.cpp through commit 97f06e9, when started with the --reranking flag, allows remote attackers to cause a denial of service (std::bad_alloc and HTTP 500) via a negative top_n value in a POST request to /rerank.

How urgent is CVE-2026-52132?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Software pages

OpenAI and LLM tools vulnerabilities

Related CVEs

CVE-2026-34159 CRITICAL 9.8 UPGRADE llama.cpp is an inference of several LLM models in C/C++
CVE-2026-70640 HIGH 7.0 UPGRADE llama.cpp builds b1886 through b7445 contain a race condition use-after-free vulnerability in the LLaMA-Androi
CVE-2026-70638 HIGH 7.8 UPGRADE llama.cpp builds b1886 through b7445 contain an integer overflow vulnerability in the LLaMA-Android JNI wrappe
CVE-2026-70639 MEDIUM 5.5 UPGRADE llama.cpp builds b1886 through b7445 contain a null pointer dereference vulnerability in the LLaMA-Android JNI
CVE-2026-43629 HIGH 8.1 UPGRADE llama.cpp builds b4882 through b9058 contain a heap buffer overflow vulnerability in the KV cache state restor

References

← Back to latest CVEs