Entity · DiggingBeagle record

Agent Router

Kubernetes and Envoy AI traffic and MCP routing project with security fixes in version 1.2.1.

Record description

Agent Router manages AI-provider traffic and Model Context Protocol (MCP) routes through an Envoy frontend and a co-located extproc component. Its November 2026 security reports distinguish header trust, session-to-route authorization, controller availability, secret custody, provider response parsing and prompt visibility. The shared product does not make these flaws one exploit: each requires a separate entry point and has a different affected operation. Version 1.2.1 is the published repair target in the reviewed release.

A controller-local OAuth metadata parser can still become a cluster-wide failure point: an isolated test of a 40 MiB metadata response killed a 160 MiB controller three times and stalled reconciliation in another namespace for 43 seconds. This is independent of the per-request Envoy trusted-header bypass and of session-to-route binding. Together, the six 1.2.1 advisories concern separate control boundaries, not six confirmed attacks against deployed customers.

Declared connections