Skip to content

OBS-2026-000593: CVE-2026-86060

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

Target Entity: CVE-2026-86060 โ€” MikroTik RouterOS SSH Argument Delimiter Injection to Administrative Takeover (MikroTrick)

MODE: RETROSPECTIVE

Methodology: HTS-3.1
Observed UTC:
2026-09-03T00:00:00.000Z
Event Date:
2026-09-03
Epistemic State:
โ— KNOWN
Cryptographic Digest:
sha256-ffd25dfe80cbac6โ€ฆ

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

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

๐Ÿšจ Listed in CISA KEV

Exploit Maturity: weaponized

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

Evidence Integrity99%
Model Stability98%
Data Completeness95%
Actionable Decisiveness96%

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

  • MikroTik Security Advisory - MikroTrick (CVE-2026-67276, CVE-2026-86060)
  • CERT Polska Technical Advisory - MikroTrick Vulnerabilities
  • CISA Known Exploited Vulnerabilities Catalog

Primary Source โ†’ OBS-2026-000593 โ†’ CVE-2026-86060 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2026-86060:

  • Preceding Observation: None (Initial Baseline)
  • Succeeding Observation: OBS-2026-000594
Observation IDDateModeScoreObserved Fact
๐Ÿ‘‰ OBS-2026-0005932026-09-03RETROSPECTIVE94Initial baseline observation created upon public disclosure and ingestion.
OBS-2026-0005942026-09-10RETROSPECTIVE94State 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-000593.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000593.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--7efbc7df-2e87-d7e3-e770-e16d7cf70321",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-09-03T00:00:00.000Z",
"modified": "2026-09-03T00:00:00.000Z",
"first_observed": "2026-09-03T00:00:00.000Z",
"last_observed": "2026-09-03T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000593",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000593/"
}
],
"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-ffd25dfe80cbac6382ab23d938b9e7dca372b6298a536e92c44c54ce1627706d"
}
}