Skip to content

OBS-2026-000251: CVE-2025-39682

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

Target Entity: CVE-2025-39682 — Linux Kernel kTLS Receive Path Zero-Length Record UAF

MODE: LIVE

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

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

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

🚨 Listed in CISA KEV

Exploit Maturity: weaponized

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

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

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

  • CISA KEV
  • NVD
  • Hermes Codex Research

Primary Source → OBS-2026-000251 → CVE-2025-39682 → 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-2025-39682:

Observation IDDateModeScoreObserved Fact
OBS-2025-0000292025-08-20RETROSPECTIVE65Initial disclosure in net/tls/tls_sw.c; vendor patches issued.
👉 OBS-2026-0002512026-09-18LIVE94CISA adds to KEV catalog with mandatory BOD 22-01 remediation deadline.
OBS-2026-0000302026-09-19LIVE94Hermes confirms weaponized exploitation across enterprise Linux fleets.

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-000251.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000251.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--fdd479cb-b46a-da5d-a2cc-d8f6961523c8",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-09-18T00:00:00.000Z",
"modified": "2026-09-18T00:00:00.000Z",
"first_observed": "2026-09-18T00:00:00.000Z",
"last_observed": "2026-09-18T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000251",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000251/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 94,
"x_hermes_severity": "CRITICAL",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-d468d6312b0676d08cc02d21e01e75da2bbfc1bf57688d5c1a73905f1a367209"
}
}