Patch, Contain, and Recontract for Cyber and Memory Risks

What happened

Arista disclosed a critical, unauthenticated OS command‑injection in VeloCloud Orchestrator (CVE-2026-16812) that is being actively exploited and was added to the KEV list. The on‑prem orchestrator is exposed by default and Arista advises restricting the web interface to trusted management networks until fixes are applied. Operationally this creates immediate patch and isolation work for buyers that run self‑hosted SD‑WAN orchestration; watch for supplier emergency SLA demands and rapid exploit telemetry updates

Why the category manager should care

Isolate or patch on‑prem orchestrators and verify vendor emergency support and liability positions; treat this as an operational priority

Key facts

• Unauthenticated OS command‑injection vulnerability (CVE-2026-16812)
• KEV listing with evidence of active exploitation
• Vendor guidance to restrict management‑interface access until patched

What happened

JFrog released fixes after zero‑days in Artifactory were implicated in cross‑organization access; some of the vulnerabilities were discovered during AI‑model security evaluations. Artifactory hosts many package formats used across CI/CD and model marts, which makes unpatched instances a high‑impact supply‑chain dependency. Buyers should verify patch cadence, demand proof‑of‑fix artifacts, and consider managed hosting for critical pipelines to limit CI/CD blast radius

Why the category manager should care

Require documented patch SLAs, proof‑of‑fix evidence, and tenant isolation in artifact‑hosting contracts

Key facts

• Multiple Artifactory CVEs patched by vendor
• Vulnerabilities surfaced during AI‑model security testing
• Artifactory supports 60+ package formats used in delivery pipelines

What happened

SK Hynix announced it has struck multiple long‑term supply deals with large AI customers and described contract mechanisms that smooth memory prices and improve demand visibility. The company cited deposit and volume commitments as part of these arrangements, indicating suppliers are formalizing prioritization in exchange for commitment. Procurement should prepare for fewer spot opportunities and negotiate deposit, pass‑through, and allocation protections when pursuing memory buys

Why the category manager should care

Open commercial reviews with memory suppliers to understand deposit terms, minimums, and allocation priorities

Key facts

• Multiple long‑term supply deals announced with major AI customers
• Deals include deposit mechanics and pricing‑smoothing provisions
• Supplier expectation of continued strong demand for HBM and DRAM

What happened

The Model Context Protocol (MCP) received an enterprise‑focused update that removes legacy stateful requirements, adds a feature lifecycle/deprecation policy, and introduces a security enhancement to validate an issuer (iss) parameter. The change lowers integration complexity for scalable deployments but creates a defined migration window and an expectation of auth handling in supplier code. Buyers running agentic AI should require suppliers to document MCP migration support and auth validation in proposals

Why the category manager should care

Add MCP migration and issuer‑auth validation to vendor RFPs and integration checklists

Key facts

• Spec removes sticky, stateful architecture requirement for large deployments
• Introduces feature lifecycle / deprecation policy with minimum notice
• Adds an SEP requiring issuer (iss) validation in authorization responses