Skip to content

OBS-2025-000025: CVE-2025-26319

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-2025-000025

Target Entity: CVE-2025-26319 — Flowise Arbitrary File Upload and Directory Traversal Remote Code Execution

MODE: RETROSPECTIVE

Methodology: HTS-3.1
Observed UTC:
2025-02-18T00:00:00.000Z
Event Date:
2025-02-18
Epistemic State:
● KNOWN
Cryptographic Digest:
sha256-2c9f4e187867cfb…

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

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

🛡️ Not in KEV

Exploit Maturity: functional

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

Evidence Integrity94%
Model Stability96%
Data Completeness75%
Actionable Decisiveness85%

Observation OBS-2025-000025 is strictly anchored to verified records from the following primary entities:

  • NVD CVE-2025-26319 Official Advisory
  • FlowiseAI Security Bulletin

Primary Source → OBS-2025-000025 → CVE-2025-26319 → 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-26319:

  • Preceding Observation: None (Initial Baseline)
  • Succeeding Observation: OBS-2026-000026
Observation IDDateModeScoreObserved Fact
👉 OBS-2025-0000252025-02-18RETROSPECTIVE96Initial baseline observation created upon public disclosure and ingestion.
OBS-2026-0000262026-09-18RETROSPECTIVE96State change observed: threat score adjusted by +0 points; CISA KEV or weaponized exploit verified.

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-2025-000025.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2025-000025.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--1c33e0ef-480e-6196-4d2f-81fdba370b39",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2025-02-18T00:00:00.000Z",
"modified": "2025-02-18T00:00:00.000Z",
"first_observed": "2025-02-18T00:00:00.000Z",
"last_observed": "2025-02-18T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2025-000025",
"url": "https://hermes-codex.vercel.app/observations/obs-2025-000025/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 96,
"x_hermes_severity": "EXTREME",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-2c9f4e187867cfb3f2ce17095b4ed9555a5d5b3535b5e9a1cc62c75a65275de7"
}
}