Skip to content

OBS-2026-000275: CVE-2026-116779

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

Target Entity: CVE-2026-116779 โ€” SignalWire FreeSWITCH SIP MESSAGE Protocol Handling Command Injection

MODE: LIVE

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

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

Hermes Threat Score (HTS)
97 / 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)
34.2%
Percentile: 98.8th
Weaponization & CISA KEV

๐Ÿšจ Listed in CISA KEV

Exploit Maturity: active_in_the_wild

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

Evidence Integrity99%
Model Stability98%
Data Completeness95%
Actionable Decisiveness96%

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

  • CISA Known Exploited Vulnerabilities Catalog โ€” CVE-2026-116779
  • SignalWire FreeSWITCH Security Advisory โ€” mod_sofia Chat Protocol Injection
  • NIST NVD โ€” CVE-2026-116779 Detail
  • Shadowserver Sensor Telemetry โ€” Telephony Perimeter Scanning Alert

Primary Source โ†’ OBS-2026-000275 โ†’ CVE-2026-116779 โ†’ Risk Trajectory โ†’ Action Directive



Chronological lineage for entity CVE-2026-116779:

  • Preceding Observation: None (Initial Baseline)
  • Succeeding Observation: OBS-2026-000276
Observation IDDateModeScoreObserved Fact
๐Ÿ‘‰ OBS-2026-0002752026-11-06LIVE97Initial baseline observation created upon public disclosure and ingestion.
OBS-2026-0002762026-11-10LIVE97State 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-000275.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000275.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--cf5accb9-821b-fba5-f8b0-7a3777159bbe",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-11-06T00:00:00.000Z",
"modified": "2026-11-06T00:00:00.000Z",
"first_observed": "2026-11-06T00:00:00.000Z",
"last_observed": "2026-11-06T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000275",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000275/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 97,
"x_hermes_severity": "EXTREME",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-453b1c7dd91949f8688151424393cb6ed36d5362275ba69963f0ede42b64c404"
}
}