Live › vulnerability › CVE-2026-103091
Go to dashboardGoogle SAM (Sovereign/OSS Agent Mesh) before 0.1.0-alpha.9: GET /info is unauthenticated and leaks OIDC config, POST /register auto-enrolls anyone with a valid token from the configured OIDC provider (no claim filtering, no ban check), and the shipped default policy binds sam:system:authenticated to wildcard services and targets. An enrolled attacker can invoke any tool on any MCP backend node (read/write/exec). A one-hour OIDC token yields a 90-day credential, and bans are bypassed by regenerating the keypair. The vendor advisory scores it CVSS 3.1 9.8. NVD lists alpha.1 to alpha.8 and applies to default config; custom restrictive policy bindings reduce impact.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| google/sam (Agent Mesh) | go | < 0.1.0-alpha.9 | 0.1.0-alpha.9 |
v0.1.0-alpha.9; test whether GET <control-plane>/info answers without auth from outside; review your policy for sam:system:authenticated bound to wildcard services/targets; list enrolled nodes and /register logs for unknown identities; check your OIDC provider is not open to arbitrary sign-upsv0.1.0-alpha.9 (fail-closed default policy, explicit policy binding on enrollment, ban checks)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Missing Authorization (CWE-862) and Initialization of a Resource with an Insecure Default (CWE-1188) in the MCP proxy (HandleStreamPassThrough in mcp_service.go) and OIDC registration flow (GET /info and POST /register in internal/controlplane/server.go) in Google OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.8 allow a remote attacker to self-enroll into the mesh and invoke arbitrary tools across all connected MCP backend nodes. Because GET /info publicly discloses OIDC configuration, POST /register auto-enrolls any valid OIDC token holder without claim filtering or ban checks, and the default policy binds sam:system:authenticated to wildcard services and targets, an attacker can obtain a mesh credential with full read, write, and execution access on backend services. Users should upgrade to version 0.1.0-alpha.9 or later, which enforces a fail-closed default policy, explicit policy-binding requirements on enrollment, and ban checks.
This page as .md · .json · in your agent: get_signal("CVE-2026-103091")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.