CVE-2026-102503 Google CVE debrief

Who should care

Defenders responsible for Google OSS Agent Mesh (SAM) deployments should assess exposure and prioritize upgrading to version 0.1.0-alpha.3 or later. They should also verify the authenticity of libp2p peers and review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-102503 is a critical vulnerability in Google OSS Agent Mesh (SAM) that allows unauthenticated remote libp2p peers to bypass Biscuit capability policy enforcement and invoke arbitrary registered backend services. Defenders should prioritize upgrading to version 0.1.0-alpha.3 or later and verify the authenticity of libp2p peers.

• Potential unauthorized access to backend services
• Possible invocation of arbitrary registered backend services
• Bypass of Biscuit capability policy enforcement
• Verification of libp2p peer authenticity required

Technical summary

The /libp2p-http ingress server in Google OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.2 is vulnerable to CWE-306 and CWE-862, allowing unauthenticated remote libp2p peers to bypass Biscuit capability policy enforcement and invoke arbitrary registered backend services. The MCP protocol stream handler enforces WithBiscuitAuth and Authorize checks, but the parallel /libp2p-http ingress routes requests directly to backend service handlers without verifying a Biscuit token or mesh enrollment. This could lead to potential unauthorized access to backend services and possible invocation of arbitrary registered backend services.

Defensive priority

Defenders should prioritize upgrading to version 0.1.0-alpha.3 or later and verify the authenticity of libp2p peers.

Recommended defensive actions

• Upgrade to version 0.1.0-alpha.3 or later
• Verify the authenticity of libp2p peers
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, its impact, and recommended actions. The vulnerability has been reported in Google OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.2. There is no information available on known or unknown affected scope. Defenders should verify the authenticity of libp2p peers and review compensating controls for exposed systems while remediation is scheduled and verified.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.