Skip to content

OBS-2025-000097: CVE-2025-59528

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

Target Entity: CVE-2025-59528 โ€” Flowise CustomMCP Node JavaScript Function Constructor Remote Code Execution

MODE: RETROSPECTIVE

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

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

Hermes Threat Score (HTS)
99 / 100
EXTREME
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)
81.2%
Percentile: 98.5th
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-000097 is strictly anchored to verified records from the following primary entities:

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

Primary Source โ†’ OBS-2025-000097 โ†’ CVE-2025-59528 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2025-59528:

  • Preceding Observation: None (Initial Baseline)
  • Succeeding Observation: OBS-2026-000098
Observation IDDateModeScoreObserved Fact
๐Ÿ‘‰ OBS-2025-0000972025-08-04RETROSPECTIVE99Initial baseline observation created upon public disclosure and ingestion.
OBS-2026-0000982026-09-18RETROSPECTIVE99State 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-2025-000097.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2025-000097.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--2c98b365-8d6c-fb05-c707-cd9a9d9f07ce",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2025-08-04T00:00:00.000Z",
"modified": "2025-08-04T00:00:00.000Z",
"first_observed": "2025-08-04T00:00:00.000Z",
"last_observed": "2025-08-04T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2025-000097",
"url": "https://hermes-codex.vercel.app/observations/obs-2025-000097/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 99,
"x_hermes_severity": "EXTREME",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-a510a1543d184662e1eefff94c1e7dd8ebb30af4006d9a44536101d0b844e441"
}
}