CVE Tools
Track your stack

CVE-2026-102503

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

No known exploitation. EPSS puts it in the 37th percentile. Fixed in 0.1.0-alpha.3.

CVSS —Not scoredEPSS percentile37th0.4% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix0.1.0-alpha.3Upgrade to this build

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Google SAMAffected: ≥ 0.1.0-alpha.1, < 0.1.0-alpha.3Upgrade to: 0.1.0-alpha.3Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS37th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 37th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, att&ck mapped, record updated, record updated, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 1 more reference. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for SAM, not every advisory.