Skip to content

OBS-2026-000520: CVE-2026-72898

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

Target Entity: CVE-2026-72898 โ€” Metabase Pre-Authentication SQL Injection in Password Reset via HoneySQL Bypass

MODE: RETROSPECTIVE

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

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

Hermes Threat Score (HTS)
98 / 100
CRITICAL
CVSS v3.1
10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (30-Day Exploitation)
92.5%
Percentile: 99.4th
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-000520 is strictly anchored to verified records from the following primary entities:

  • The Shadowserver Foundation Sensor Telemetry: Metabase CVE-2026-72898 In-The-Wild Exploitation
  • Metabase Security Advisory: Pre-Auth SQL Injection in Password Reset Endpoint
  • CERT-FR Alerte Cyber: Vulnรฉrabilitรฉ critique dans Metabase CVE-2026-72898
  • NIST National Vulnerability Database CVE-2026-72898

Primary Source โ†’ OBS-2026-000520 โ†’ CVE-2026-72898 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2026-72898:

  • Preceding Observation: None (Initial Baseline)
  • Succeeding Observation: OBS-2026-000521
Observation IDDateModeScoreObserved Fact
๐Ÿ‘‰ OBS-2026-0005202026-08-06RETROSPECTIVE98Initial baseline observation created upon public disclosure and ingestion.
OBS-2026-0005212026-10-10LIVE98State 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-000520.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000520.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--c5b5561c-267e-96b2-10e2-a50c8a1407d3",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-08-06T00:00:00.000Z",
"modified": "2026-08-06T00:00:00.000Z",
"first_observed": "2026-08-06T00:00:00.000Z",
"last_observed": "2026-08-06T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000520",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000520/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 98,
"x_hermes_severity": "CRITICAL",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-e9db3567e9f8cdb814c3e94e6887f1c7137312d41003a4e628cd82b5a93efd5d"
}
}