OBS-2026-000159: CVE-2026-77257

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

Target Entity: CVE-2026-77257 — mcp-atlassian Jira Upload Attachment Path Traversal

MODE: LIVE

Methodology: HTS-3.1

Observed UTC:
2026-09-22T00:00:00.000Z

Event Date:
2026-09-22T00:00:00.000Z

Epistemic State:
● KNOWN

Cryptographic Digest:
sha256-626d4c23e1f1878…

1. Verified Evidence & Observed State

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

Hermes Threat Score (HTS)

83 / 100

HIGH

CVSS v3.1

8.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS (30-Day Exploitation)

15.0%

Percentile: 75.0th

Weaponization & CISA KEV

🛡️ Not in KEV

Exploit Maturity: none

2. Decomposed Epistemic Confidence Vector

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

Evidence Integrity88%

Model Stability90%

Data Completeness75%

Actionable Decisiveness85%

3. Primary Sources & Provenance Chain

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

NVD CVE-2026-77257 Advisory

Causal Intelligence Lineage

Primary Source → OBS-2026-000159 → CVE-2026-77257 → Risk Trajectory → Action Directive

4. Target Entity & Correlated Intelligence

Primary Vulnerability Dossier: CVE-2026-77257
Impacted Software Product : mcp-atlassian (Model Context Protocol) (sooperset ecosystem)
Dynamic Risk Trajectories: View risk trajectory analysis
Decision Engine: View prescriptive remediation directives

5. Observation Sequence & Chain of Custody

Chronological lineage for entity CVE-2026-77257:

Preceding Observation: None (Initial Baseline)
Succeeding Observation: None (Latest Observation)

Observation ID	Date	Mode	Score	Observed Fact
👉 `OBS-2026-000159`	`2026-09-22T00:00:00.000Z`	LIVE	83	Initial baseline observation created upon public disclosure and ingestion.

6. Reproducibility & Cryptographic Verification

(Section 77 Mandate: “Observations must be reproducible”)

Fetch and verify this observation record directly from the machine-readable API:

# 1. Fetch canonical observation record
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000159.json

# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000159.json | sha256sum

OASIS STIX 2.1 Mapping (`observed-data`)

{
  "type": "observed-data",
  "spec_version": "2.1",
  "id": "observed-data--b6229d8b-8e19-e529-cf31-05eea921aaa8",
  "created_by_ref": "identity--hermes-codex-threat-observatory",
  "created": "2026-09-22T00:00:00.000Z",
  "modified": "2026-09-22T00:00:00.000Z",
  "first_observed": "2026-09-22T00:00:00.000Z",
  "last_observed": "2026-09-22T00:00:00.000Z",
  "number_observed": 1,
  "external_references": [
    {
      "source_name": "hermes-codex",
      "external_id": "OBS-2026-000159",
      "url": "https://hermes-codex.vercel.app/observations/obs-2026-000159/"
    }
  ],
  "object_marking_refs": [
    "marking-definition--tlp-clear"
  ],
  "custom_properties": {
    "x_hermes_threat_score": 83,
    "x_hermes_severity": "HIGH",
    "x_hermes_epistemic_state": "KNOWN",
    "x_hermes_methodology": "HTS-3.1",
    "x_hermes_integrity_hash": "sha256-626d4c23e1f187800ba0b7fc406c94c126eb84b4d56d8d82b0ff0d0d91c10930"
  }
}