Skip to content

OBS-2026-000278: CVE-2026-118527

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

Target Entity: CVE-2026-118527 โ€” Ivanti Connect Secure & Policy Secure Predictable Session Identifier Generation & Administrative Authentication Bypass (CISA KEV)

MODE: LIVE

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

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

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

๐Ÿšจ Listed in CISA 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-000278 is strictly anchored to verified records from the following primary entities:

  • CISA Known Exploited Vulnerabilities Catalog โ€” CVE-2026-118527
  • Ivanti Security Advisory โ€” CVE-2026-118527
  • NIST National Vulnerability Database โ€” CVE-2026-118527

Primary Source โ†’ OBS-2026-000278 โ†’ CVE-2026-118527 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2026-118527:

  • Preceding Observation: OBS-2026-000277
  • Succeeding Observation: None (Latest Observation)
Observation IDDateModeScoreObserved Fact
OBS-2026-0002772026-10-30LIVE97Initial baseline observation created upon public disclosure and ingestion.
๐Ÿ‘‰ OBS-2026-0002782026-10-31LIVE97State 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-000278.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000278.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--c2160970-c041-8b9c-ba0c-e09d8e8d57e5",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-10-31T00:00:00.000Z",
"modified": "2026-10-31T00:00:00.000Z",
"first_observed": "2026-10-31T00:00:00.000Z",
"last_observed": "2026-10-31T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000278",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000278/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 97,
"x_hermes_severity": "CRITICAL",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-13ed1a831ad50a8b1d2853b945c01c1435cf3c6fa794967171d0c105f52a4ac5"
}
}