CVE-2024-58400

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7wfj-q343-9m2r ↗EUVD-2024-55827 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ggml-org llama.cpp < b3701
fixed in b3701
CWE-129 Improper Validation of Array Index
ETK-2026-2713Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 29msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h58m
0
+2h
+6h
+8h
+10h
+12h

description

llama.cpp releases before b3701 are affected by an out-of-bounds read in token processing. An unauthenticated remote user able to reach the llama-server completion endpoint may trigger memory disclosure or crash the process by submitting invalid token IDs.

mitigation

Upgrade llama.cpp to build b3701 or later. Until upgrading, restrict unauthenticated access to the llama-server completion endpoint.

fixed in b3701

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 00:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-27 00:33Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2024-58400

{
  "etk_id": "ETK-2026-2713",
  "cve_id": "CVE-2024-58400",
  "display_id": "CVE-2024-58400",
  "ghsa_id": "GHSA-7wfj-q343-9m2r",
  "euvd_id": "EUVD-2024-55827",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in llama.cpp token handling",
  "summary": "llama.cpp releases before b3701 are affected by an out-of-bounds read in token processing. An unauthenticated remote user able to reach the llama-server completion endpoint may trigger memory disclosure or crash the process by submitting invalid token IDs.",
  "mitigation": "Upgrade llama.cpp to build b3701 or later. Until upgrading, restrict unauthenticated access to the llama-server completion endpoint.",
  "vendor": "ggml-org",
  "product": "llama.cpp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < b3701"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "b3701"
      ],
      "package_name": "llama.cpp",
      "purl": null
    }
  ],
  "cwes": [
    129
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.330430233333335,
  "t0_at": "2026-10-27T00:33:57.354000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T00:33:57.354000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T00:33:57.354000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-58400"
    }
  }
}

published 2026-10-27 01:28Z
last change 2026-10-27 06:37Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.