Skip to content

OBS-2026-000256: CVE-2026-32626

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-000256

Target Entity: CVE-2026-32626 — AnythingLLM Desktop Streaming Phase XSS to Host RCE

MODE: RETROSPECTIVE

Methodology: HTS-3.1
Observed UTC:
2026-09-17T00:00:00.000Z
Event Date:
2026-09-17
Epistemic State:
● KNOWN
Cryptographic Digest:
sha256-e5b8436dec70846…

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

Hermes Threat Score (HTS)
60 / 100
MEDIUM
CVSS v3.1
N/A
Not Available
EPSS (30-Day Exploitation)
N/A
Percentile: N/A
Weaponization & CISA KEV

🛡️ Not in KEV

Exploit Maturity: poc

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

Evidence Integrity98%
Model Stability96%
Data Completeness95%
Actionable Decisiveness95%

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

  • CISA KEV
  • NVD
  • Hermes Codex Research

Primary Source → OBS-2026-000256 → CVE-2026-32626 → Risk Trajectory → Action Directive


4. Target Entity & Correlated Intelligence

Section titled “4. Target Entity & Correlated Intelligence”

5. Observation Sequence & Chain of Custody

Section titled “5. Observation Sequence & Chain of Custody”

Chronological lineage for entity CVE-2026-32626:

Observation IDDateModeScoreObserved Fact
OBS-2026-0000632026-04-10RETROSPECTIVE95Initial baseline observation created upon public disclosure and ingestion.
👉 OBS-2026-0002562026-09-17RETROSPECTIVE60Unescaped image alt tag in markdown renderer discovered.
OBS-2026-0000642026-09-19LIVE88Demonstrated Electron IPC escape via RAG document indirect prompt injection.
OBS-2026-0002582026-09-20LIVE88Mintplex Labs releases patch v1.11.2 enforcing DOMPurify during streaming.

6. Reproducibility & Cryptographic Verification

Section titled “6. Reproducibility & Cryptographic Verification”

(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-000256.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000256.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--98240be8-6f4a-c07c-bc8b-a14cf0a9c845",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-09-17T00:00:00.000Z",
"modified": "2026-09-17T00:00:00.000Z",
"first_observed": "2026-09-17T00:00:00.000Z",
"last_observed": "2026-09-17T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000256",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000256/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 60,
"x_hermes_severity": "MEDIUM",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-e5b8436dec70846dbf6b5192a9ddf7b452a11d291491857cd881d4668c95f2ab"
}
}