Live › vulnerability › CVE-2026-102503
Go to dashboardGoogle OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.2 expose a /libp2p-http ingress that forwards requests to backend services without checking Biscuit tokens or mesh enrollment. An unauthenticated remote libp2p peer can invoke any registered backend, including command-backed MCP servers, A2A and inference endpoints.
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.
No product ranges from the sources yet.
Check the installed SAM version and confirm it is 0.1.0-alpha.1 or 0.1.0-alpha.2.
Upgrade to version 0.1.0-alpha.3 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Missing Authentication for Critical Function (CWE-306) and Missing Authorization (CWE-862) in the /libp2p-http ingress server (StartIngressServer in cmd/sam-node/node.go) in Google OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.2 allow an unauthenticated remote libp2p peer to bypass Biscuit capability policy enforcement and invoke arbitrary registered backend services (including command/stdio-backed MCP servers, A2A, and inference endpoints). While the MCP protocol stream handler enforces WithBiscuitAuth and Authorize checks, the parallel /libp2p-http ingress routes requests directly to backend service handlers without verifying a Biscuit token or mesh enrollment. Users should upgrade to version 0.1.0-alpha.3 or later.
This page as .md · .json · in your agent: get_signal("CVE-2026-102503")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.