ThreatModeling

What CVE-2026-20127 Reveals About Your Management Plane’s Trust Model

by
Network operations center with rows of monitoring screens displaying network status dashboards, CVE-2026-20127 management plane environment

Cisco’s SD-WAN peering authentication existed in the architecture, appeared in threat models, and passed functional tests — for three years. It never enforced. CVE-2026-20127 reveals a design failure recurring across vendors: authentication gates running after request classification, creating request classes that bypass identity verification. Does any request path reach your processing logic before authentication runs?

Runtime Security Boundaries Require Runtime Enforcement: Lessons from n8n’s CVE Chain

by
Isometric diagram showing a dark server chassis with an expression evaluator unit. An empty mounting frame at the evaluator's input boundary has no barrier plate installed. An amber signal beam passes through the empty frame and strikes the execution module, which glows amber. Teal circuit traces terminate at the frame edge without connecting to the execution path.

n8n’s five critical CVEs in 90 days share a single architectural flaw: TypeScript type annotations used as runtime security enforcement — but TypeScript annotations don’t exist at JavaScript runtime. The patch for the first CVE was bypassed by the same mechanism two months later. If you build AI agent pipelines or any sandbox with compile-time security constraints, this CVE chain names the failure directly.

What GRP-Obliteration Tells You About Your AI System’s Threat Model

by

Microsoft researchers reversed LLM safety alignment across 15 models using a single adversarial training prompt. The attack exploits a fundamental design flaw: safety implemented as learned behavior can be inverted through training-based attacks. For product security teams deploying AI systems, the lesson is architectural – security properties must be enforced through system design, not statistical tendencies.