Skip to content
MediumVulnerability

GHSA-953h-535j-jg2v: agent-router: MCP session resume does not verify the embedded anti-hijacking subject; default Helm seed makes session IDs forgeable

Published
Record updated
View JSON
Affected
  • github.com/envoyproxy/ai-gateway >= 0.4.0-rc1, < 1.2.0-rc1
Fixed in
1.2.0-rc1

Summary

The Envoy AI Gateway MCP proxy's session-resume path never checks the subject (JWT `sub` claim) embedded in the client-facing session ID, so any client holding a session ID can resume another user's session and invoke backend methods such as `tools/call` and `resources/read`. The official Helm chart aggravates this by defaulting the session encryption seed to the publicly known `"default-insecure-seed"`, which would let an attacker forge session IDs.

Mitigation

The source does not state a fix yet. Check the original advisory for updates.