Skip to content

OBS-2025-000101: CVE-2025-6514

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

Target Entity: CVE-2025-6514 โ€” mcp-remote Proxy OS Command Injection via Malicious MCP Server OAuth Metadata

MODE: RETROSPECTIVE

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

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

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

๐Ÿ›ก๏ธ Not in KEV

Exploit Maturity: functional

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

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

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

  • JFrog Security Research (MCP-Remote RCE)
  • National Vulnerability Database (NVD)

Primary Source โ†’ OBS-2025-000101 โ†’ CVE-2025-6514 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2025-6514:

  • Preceding Observation: None (Initial Baseline)
  • Succeeding Observation: OBS-2026-000102
Observation IDDateModeScoreObserved Fact
๐Ÿ‘‰ OBS-2025-0001012025-06-25RETROSPECTIVE94Initial baseline observation created upon public disclosure and ingestion.
OBS-2026-0001022026-10-09LIVE94State 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-000101.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2025-000101.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--e81597bf-577d-e902-7cb8-feccdb8d0167",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2025-06-25T00:00:00.000Z",
"modified": "2025-06-25T00:00:00.000Z",
"first_observed": "2025-06-25T00:00:00.000Z",
"last_observed": "2025-06-25T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2025-000101",
"url": "https://hermes-codex.vercel.app/observations/obs-2025-000101/"
}
],
"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-d9e50f825279f832de91357eac5dcdb8cf2191a34c993299efe082f385231b4d"
}
}