CVE-2026-102503: Missing Authentication on /libp2p-http Ingress in Google OSS Agent Mesh (SAM)

Published Oct 19, 2026
·
Updated

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.

Affected Software

1 affected component
Google OSS Agent Mesh (SAM)>=0.1.0-alpha.1<=0.1.0-alpha.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Google OSS Agent Mesh (SAM) to a version that resolves this vulnerability.

    Fixed in 0.1.0-alpha.3

Event History

Oct 19, 2026
CVE Published
via MITRE·02:20 AM
Data Sourced
via MITRE·02:20 AM
DescriptionWeakness
Data Sourced
via NVD·03:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Google OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.2 are affected when the /libp2p-http ingress server is in use. The affected ingress can route requests to registered backend services, including command/stdio-backed MCP servers, A2A, and inference endpoints.

2

What does an attacker need to exploit it?

An attacker needs only remote libp2p connectivity to the affected ingress. No authentication, Biscuit token, mesh enrollment, or prior privileges are required.

3

Does the existing Biscuit policy enforcement protect these requests?

No. Although the MCP protocol stream handler performs Biscuit authentication and authorization checks, the parallel /libp2p-http ingress routes requests directly to backend handlers without those checks.

4

How should this be remediated?

Upgrade SAM to version 0.1.0-alpha.3 or later. The provided information does not specify a workaround for deployments that cannot yet upgrade.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203