{
  "version": "1.0",
  "last_updated": "2026-11-17T11:08:58.640Z",
  "total_dispatches": 3,
  "methodology": "HSD-1.0",
  "dispatches": [
    {
      "id": "DISPATCH-2026-10-09-BRIEF",
      "date": "2026-10-09",
      "type": "DAILY_BRIEF",
      "title_en": "Emergency CISA KEV Additions, Bricksforge RCE & Agentic llama.cpp Parsing Flaws",
      "title_fr": "Vague d'ajouts CISA KEV, RCE Bricksforge & Failles de parsing agentique llama.cpp",
      "url": "https://hermes-codex.vercel.app/threat-intel/daily-brief/2026-10-09/",
      "channels": {
        "twitter": [
          "🚨 1/5 [HERMES THREAT DISPATCH] Critical perimeter & agentic vulnerabilities observed in the last 24h.\n\n• Bricksforge WP RCE (CVE-2026-85097, HTS 96)\n• 5 CISA KEV additions (ONLYOFFICE, SonicWall, Struts, ProFTPD, BIND 9)\n• llama.cpp tool parsing UAF (CVE-2026-107183)",
          "🔍 2/5 In CMS perimeters, Bricksforge (CVE-2026-85097) suffers active unauth file upload. Attackers bypass client validation to drop executable PHP/GIF polyglots.\n\nSimultaneously, CISA adds ONLYOFFICE Document Server (CVE-2021-3199) to KEV due to weaponized JWT traversal.",
          "🤖 3/5 In Agentic AI runtimes, llama.cpp (CVE-2026-107183, HASS 96) exposes a critical heap UAF & double-free during grammar-constrained tool parsing. Adversarial tool schemas trigger arbitrary memory corruption during autonomous agent loops.",
          "🛡️ 4/5 Prescriptive Actions (T0 < 24h):\n1. Patch Bricksforge to >= 2.3.4 or restrict /upload endpoint.\n2. Isolate ONLYOFFICE DocService behind strict WAF canonical path filters.\n3. Update llama.cpp agent inference backends to release 2026-10-08.",
          "📊 5/5 Full forensic telemetry, risk velocity curves, and automated SOAR playbooks (Cortex XSOAR, Splunk, Tines, Ansible):\n\n👉 https://hermes-codex.vercel.app/threat-intel/daily-brief/2026-10-09/\n\n#CyberSecurity #ThreatIntel #InfoSec #AgenticAI #CISA"
        ],
        "linkedin": "🚨 EXECUTIVE THREAT ADVISORY | CISA KEV Emergency Additions & Agentic AI Runtimes Under Fire\n\nOver the last 24 hours, the Hermes Codex Autonomous Intelligence Observatory has tracked two concurrent weaponization vectors impacting enterprise perimeters and emerging agentic AI architectures:\n\n1. Active Perimeter Exploitation:\n• WordPress Bricksforge Plugin (CVE-2026-85097 | Hermes Threat Score: 96/100): Unauthenticated file upload flaw currently undergoing automated exploitation in the wild.\n• CISA KEV Batch Ingestion: Official federal emergency addition of 5 historic and active flaws, led by ONLYOFFICE Document Server (CVE-2021-3199 | HTS: 94) following active JWT path traversal weaponization.\n\n2. Agentic AI Infrastructure Vulnerability:\n• llama.cpp Grammar-Constrained Parsing (CVE-2026-107183 | HASS: 96/100): A severe heap Use-After-Free flaw during autonomous tool schema validation. Malicious third-party tool responses can corrupt agent memory and achieve arbitrary remote code execution.\n\n💼 C-Level & CISO Strategic Takeaways:\nTraditional perimeter defenses fail when autonomous agents accept untrusted multi-agent tool schemas without sandboxing. Every organization deploying ReAct agent workflows must enforce kernel-level syscall isolation (eBPF/seccomp).\n\n🛡️ Immediate Prescriptive Directives:\n• T0 (<24h): Patch WordPress Bricksforge to v2.3.4 and isolate ONLYOFFICE Document Server.\n• T1 (<7d): Deploy Hermes SOAR Playbook P10 across your automation pipeline (Cortex XSOAR / Splunk / Tines).\n• T2 (<30d): Audit all LLM agent runtime engines against the Hermes Agentic Security Score (HASS).\n\nRead the complete evidence-backed intelligence brief and download automated SOAR playbooks:\n🔗 https://hermes-codex.vercel.app/threat-intel/daily-brief/2026-10-09/\n\n#CyberSecurity #CISO #RiskManagement #ThreatIntelligence #AgenticAI #InformationSecurity",
        "soc_cartouche": "┌────────────────────────────────────────────────────────────────────────────┐\\n│ [CRITICAL] HERMES CODEX CTI BROADCAST — BRIEF-2026-10-09                   │\\n├────────────────────────────────────────────────────────────────────────────┤\\n│ THREAT LEVEL: CRITICAL | EPOCH DAY: 20 | TLP: CLEAR                        │\\n│                                                                            │\\n│ 1. PERIMETER RCE: WordPress Bricksforge (CVE-2026-85097)                   │\\n│    • HTS: 96/100 | EPSS: 0.088 (+0.088) | Attack: Unauth File Upload RCE   │\\n│    • TTP: T1190 Exploit Public-Facing App -> T1059 Command Execution        │\\n│                                                                            │\\n│ 2. CISA KEV ADDITIONS: ONLYOFFICE Docs (CVE-2021-3199)                     │\\n│    • HTS: 94/100 | EPSS: 0.941 (+0.012) | Attack: JWT Path Traversal RCE   │\\n│                                                                            │\\n│ 3. AGENTIC AI RUNTIME: llama.cpp (CVE-2026-107183)                         │\\n│    • HTS: 95/100 | HASS: 96/100 | Flaw: Tool Grammar Heap UAF / Double-Free │\\n│                                                                            │\\n│ DIRECTIVE: Deploy P10 SOAR Playbooks (Cortex XSOAR, Splunk, Tines)        │\\n│ DOSSIER: https://hermes-codex.vercel.app/threat-intel/daily-brief/2026-10-09 │\\n└────────────────────────────────────────────────────────────────────────────┘",
        "newsletter": "### 🚨 Hermes Daily Risk Intelligence: 2026-10-09 Edition\n\n**Executive Summary:**\nA dual-wave weaponization day tracked by the Hermes Autonomous Observatory. WordPress Bricksforge plugin (`CVE-2026-85097`) is facing active mass exploitation, while CISA issued emergency KEV inclusion directives for ONLYOFFICE Document Server (`CVE-2021-3199`). In the agentic AI strata, runtime parsing in `llama.cpp` (`CVE-2026-107183`) reveals critical memory corruption vulnerabilities in autonomous tool-calling loops.\n\n* **Top Threat Scores:** Bricksforge (HTS 96), llama.cpp (HTS 95, HASS 96), ONLYOFFICE (HTS 94).\n* **Automated Playbooks:** Download ready-to-run SOAR playbooks for Splunk, Cortex, Tines, and Ansible.\n* **Deep Dive:** [Read the full audit brief on Hermes Codex](https://hermes-codex.vercel.app/threat-intel/daily-brief/2026-10-09/)."
      }
    },
    {
      "id": "DISPATCH-2026-10-09-ACLE-MCP",
      "date": "2026-10-09",
      "type": "AI_SECURITY",
      "title_en": "Closing the MCP Trust Gap: Attested Capability Leases for Autonomous AI",
      "title_fr": "Combler la faille de confiance MCP : Baux de capacité attestés pour l'IA autonome",
      "url": "https://hermes-codex.vercel.app/ai-security/core-studies/acle-mcp-attested-capability-leases-execution-trust/",
      "channels": {
        "twitter": [
          "🤖 1/5 [AI SECURITY BREAKTHROUGH] How do you trust an AI agent using Model Context Protocol (MCP) when human approval happens at T0, but malicious tool execution happens at T1?\n\nNew Peking University research introduces ACLE-MCP to fix the Post-Authorization Trust Gap.",
          "🔓 2/5 The vulnerability: Current agent architectures (Claude Code, Cursor, Copilot) use static tool consent. Once authorized, an injected prompt can coerce the agent into calling dangerous tools with poisoned arguments without re-prompting the human.",
          "🛡️ 3/5 ACLE-MCP solves this by replacing perpetual permissions with Attested Capability Leases: ephemeral, single-use, cryptographically signed capability tokens bound to hardware vTPM enclaves.\n\nNo valid lease = kernel drops the syscall instantly.",
          "📈 4/5 Benchmark Results:\n• Eliminates 98.7% of unauthorized tool invocations.\n• Enforces multi-party quorum signatures before sensitive file/network operations.\n• Adds only 14ms latency to agent reasoning loops.",
          "📑 5/5 Explore our deep-dive analysis, formal threat model, and cross-mapping to MCP security standards on Hermes Codex:\n\n👉 https://hermes-codex.vercel.app/ai-security/core-studies/acle-mcp-attested-capability-leases-execution-trust/\n\n#AgenticAI #AISecurity #LLM #MCP #AppSec"
        ],
        "linkedin": "🔐 SECURING THE AGENTIC ECOSYSTEM | Beyond Passive Consent in Model Context Protocol (MCP)\n\nAs AI coding assistants and autonomous agents rapidly integrate the Model Context Protocol (MCP) into enterprise infrastructure, security teams face a critical blind spot: the \"Post-Authorization Trust Gap\".\n\nIn a landmark research paper from Peking University (arXiv:2609.02690), researchers dissect how prompt injection adversaries exploit the temporal divergence between human approval and actual tool execution. Once a developer approves a tool session, the agent's context window can be manipulated via indirect injection to invoke malicious payloads without re-triggering authorization.\n\n💡 The Solution: ACLE-MCP (Attested Capability Leases)\nRather than trusting the LLM's conversational state, ACLE-MCP treats agent capabilities as ephemeral, cryptographically attested leases:\n1. Micro-Leases: Every tool execution requires a single-use token signed by an independent verifier.\n2. Hardware Enclave Attestation: Leases are bound to vTPM / confidential computing states.\n3. Channel Closure: Argument tampering is mathematically prevented before syscall dispatch.\n\n📊 Operational Performance:\n• 98.7% reduction in unauthorized autonomous tool actions.\n• Sub-15ms operational overhead.\n• Native integration with enterprise SIEM & zero-trust control planes.\n\nRead our complete architectural review, threat model analysis, and implementation roadmap on Hermes Codex:\n🔗 https://hermes-codex.vercel.app/ai-security/core-studies/acle-mcp-attested-capability-leases-execution-trust/\n\n#AgenticAI #CyberSecurity #ModelContextProtocol #AppSec #SoftwareArchitecture #ZeroTrust",
        "soc_cartouche": "┌────────────────────────────────────────────────────────────────────────────┐\\n│ [RESEARCH] HERMES CODEX AI SECURITY DOSSIER: ACLE-MCP PROTOCOL             │\\n├────────────────────────────────────────────────────────────────────────────┤\\n│ REF: arXiv:2609.02690 | TOPIC: Attested Capability Leases for MCP         │\\n│ VULN CLASS: Post-Authorization Trust Gap & Agentic Tool Hijacking          │\\n│ TARGET: Model Context Protocol (MCP) in Agentic Coding Assistants          │\\n│                                                                            │\\n│ THREAT SCENARIO: Indirect Prompt Injection in README or Source Code        │\\n│ COERCION: Exploitation of pre-authorized tool tokens to exfil data         │\\n│ COUNTERMEASURE: Ephemeral vTPM capability leases with quorum attestation   │\\n│                                                                            │\\n│ DOSSIER: https://hermes-codex.vercel.app/ai-security/core-studies/acle-mcp │\\n└────────────────────────────────────────────────────────────────────────────┘",
        "newsletter": "### 🤖 AI Security Spotlight: ACLE-MCP Solves the Post-Authorization Trust Gap\n\n**Why Static Tool Approvals Fail:**\nWhen a developer clicks \"Allow\" on an agent tool (Claude Code, Cursor, Copilot), that permission remains valid across the session. If the agent subsequently parses a poisoned webpage or repository, an indirect prompt injection can hijack that pre-approved tool to exfiltrate private codebases.\n\nResearchers have introduced **ACLE-MCP** (*Attested Capability Leases for MCP*), introducing hardware-backed, single-use cryptographically signed execution tokens. In benchmark evaluations, ACLE eliminates **98.7%** of unauthorized agent invocations with negligible latency overhead.\n\n* [Read the full technical critique and architectural review on Hermes Codex](https://hermes-codex.vercel.app/ai-security/core-studies/acle-mcp-attested-capability-leases-execution-trust/)."
      }
    },
    {
      "id": "DISPATCH-2026-10-09-BRICKSFORGE",
      "date": "2026-10-09",
      "type": "CRITICAL_PERIMETER",
      "title_en": "WordPress Bricksforge Plugin 0-Day: Unauth Arbitrary File Upload to RCE (CVE-2026-85097)",
      "title_fr": "0-Day Bricksforge WordPress : Téléversement arbitraire vers RCE sans authentification",
      "url": "https://hermes-codex.vercel.app/cve/2026/cve-2026-85097/",
      "channels": {
        "twitter": [
          "🚨 1/4 [ZERO-DAY ADVISORY] Critical unauthenticated RCE in WordPress Bricksforge plugin (CVE-2026-85097 | HTS 96/100).\n\nFlaw allows remote unauthenticated actors to upload polyglot PHP files and obtain full server takeover.",
          "💥 2/4 Vulnerability mechanics: Bricksforge endpoint fails to enforce user permission verification when processing client file uploads, relying on easily forgeable nonces. Attackers craft multipart requests to bypass extension filters.",
          "🛑 3/4 Remediation: Update immediately to Bricksforge >= 2.3.4. If patching is delayed, block all POST requests to wp-admin/admin-ajax.php containing bricksforge_upload actions via your WAF.",
          "📊 4/4 Complete vulnerability lineage, exploit payload patterns, and Sigma detection rules on Hermes Codex:\n\n👉 https://hermes-codex.vercel.app/cve/2026/cve-2026-85097/\n\n#WordPress #ZeroDay #RCE #AppSec #Vulnerability"
        ],
        "linkedin": "⚠️ CRITICAL ZERO-DAY ADVISORY | WordPress Bricksforge Plugin RCE (CVE-2026-85097)\n\nThe Hermes Codex Threat Observatory has identified active automated exploitation targeting the Bricksforge WordPress plugin (CVE-2026-85097), rated at a Critical Hermes Threat Score (HTS) of 96/100.\n\n🔍 Root Cause:\nThe vulnerability resides in the asynchronous file upload handling routines. The plugin fails to validate user capabilities prior to writing incoming files into web-accessible directories. By passing crafted multipart payloads with embedded PHP headers, unauthenticated remote attackers achieve immediate shell access.\n\n🛡️ Recommended Defensive Posture:\n1. Urgent Patching: Upgrade all WordPress instances utilizing Bricksforge to release 2.3.4 or higher immediately.\n2. Web Application Firewall: Enforce edge rules restricting unauthenticated POST requests targeting Bricksforge upload endpoints.\n3. Incident Response: Review web server access logs for anomalous POST requests to `/wp-json/bricksforge/` or `admin-ajax.php` generating unexpected .php creations.\n\nReview full technical details and detection indicators on Hermes Codex:\n🔗 https://hermes-codex.vercel.app/cve/2026/cve-2026-85097/\n\n#CyberSecurity #WordPress #AppSec #IncidentResponse #VulnerabilityManagement",
        "soc_cartouche": "┌────────────────────────────────────────────────────────────────────────────┐\\n│ [0-DAY ALERT] WORDPRESS BRICKSFORGE RCE (CVE-2026-85097)                   │\\n├────────────────────────────────────────────────────────────────────────────┤\\n│ CVE: CVE-2026-85097 | HTS: 96/100 | SEVERITY: CRITICAL                    │\\n│ COMPONENT: WordPress Bricksforge Plugin (< 2.3.4)                         │\\n│ ATTACK VECTOR: Remote Unauthenticated File Upload -> Webshell Execution   │\\n│ EXPLOIT STATUS: Active Weaponization Observed in Wild                     │\\n│                                                                            │\\n│ IOC / SIGMA: Suspicious PHP write in wp-content/uploads/bricksforge/       │\\n│ REMEDIATION: Upgrade to v2.3.4 immediately                                │\\n│ DOSSIER: https://hermes-codex.vercel.app/cve/2026/cve-2026-85097/          │\\n└────────────────────────────────────────────────────────────────────────────┘",
        "newsletter": "### ⚠️ Critical Zero-Day: WordPress Bricksforge Unauthenticated RCE (`CVE-2026-85097`)\n\n**Threat Profile:** Hermes Threat Score **96/100** | Active In-The-Wild Exploitation.\n\nA severe arbitrary file upload vulnerability in the Bricksforge WordPress plugin allows unauthenticated attackers to upload malicious PHP web shells directly into public directories. Threat actors are actively scanning for unpatched instances.\n\n* **Action Required:** Immediate upgrade to version **2.3.4**.\n* **Detection & Forensics:** [View detailed attack telemetry on Hermes Codex](https://hermes-codex.vercel.app/cve/2026/cve-2026-85097/)."
      }
    }
  ]
}