Skip to content

OBS-2026-000172: CVE-2026-107183

Density:
1. Observe What changed? โ†’
2. Understand Why does it matter? โ†’
3. Track How does risk evolve? โ†’
4. Predict What happens next? โ†’
5. Decide What to do? โ†’
6. Verify What happened? โ†’
7. Remember Persistent memory
IMMUTABLE CANONICAL OBSERVATION

OBS-2026-000172

Target Entity: CVE-2026-107183 โ€” llama.cpp Remote Heap Use-After-Free in PEG Chat Parser via Dangling Tool Pointer

MODE: LIVE

Methodology: HTS-3.1
Observed UTC:
2026-10-08T00:00:00.000Z
Event Date:
2026-10-08
Epistemic State:
โ— KNOWN
Cryptographic Digest:
sha256-307e19ff1c284cbโ€ฆ

This canonical observation confirms the following factual event on the threat surface:

Hermes Threat Score (HTS)
95 / 100
CRITICAL
CVSS v3.1
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-Day Exploitation)
4.2%
Percentile: 91.2th
Weaponization & CISA KEV

๐Ÿ›ก๏ธ Not in KEV

Exploit Maturity: weaponized

Hermes rejects false certainty and explicitly exposes its decomposed confidence vector:

Evidence Integrity99%
Model Stability97%
Data Completeness98%
Actionable Decisiveness97%

Observation OBS-2026-000172 is strictly anchored to verified records from the following primary entities:

  • VulnCheck Weaponized Advisory: llama.cpp before b11393 Use-After-Free via common_chat_peg_mapper chat_parser
  • llama.cpp Release b11393 Fix Dangling current_tool in PEG Mapper
  • NIST National Vulnerability Database CVE-2026-107183

Primary Source โ†’ OBS-2026-000172 โ†’ CVE-2026-107183 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2026-107183:

  • Preceding Observation: OBS-2026-000171
  • Succeeding Observation: None (Latest Observation)
Observation IDDateModeScoreObserved Fact
OBS-2026-0001712026-10-07LIVE95Initial baseline observation created upon public disclosure and ingestion.
๐Ÿ‘‰ OBS-2026-0001722026-10-08LIVE95State change observed: threat score adjusted by +0 points; CISA KEV or weaponized exploit verified.

(Section 77 Mandate: โ€œObservations must be reproducibleโ€)

Fetch and verify this observation record directly from the machine-readable API:

Terminal window
# 1. Fetch canonical observation record
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000172.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000172.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--7121245c-72ad-8dd7-35a4-0f2030cef7c7",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-10-08T00:00:00.000Z",
"modified": "2026-10-08T00:00:00.000Z",
"first_observed": "2026-10-08T00:00:00.000Z",
"last_observed": "2026-10-08T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000172",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000172/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 95,
"x_hermes_severity": "CRITICAL",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-307e19ff1c284cb92b3f7dd32b60e19fe703010accea4d8170d52d73ab68bf49"
}
}