Google SAM up to 0.1.0-alpha.8 Control Plane Enrollment Status server.go HandleEnrollStatus peer_id missing authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 4.09- |
Summary
A vulnerability was found in Google SAM up to 0.1.0-alpha.8. It has been rated as critical. Affected by this issue is the function HandleEnrollStatus of the file internal/controlplane/server.go of the component Control Plane Enrollment Status Handler. Performing a manipulation of the argument peer_id results in missing authentication.
This vulnerability is cataloged as CVE-2026-103090. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, was found in Google SAM up to 0.1.0-alpha.8. This affects the function HandleEnrollStatus of the file internal/controlplane/server.go of the component Control Plane Enrollment Status Handler. The manipulation of the argument peer_id with an unknown input leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Missing Authentication for Critical Function (CWE-306) and Insufficiently Protected Credentials (CWE-522) in the control plane enrollment status handler (HandleEnrollStatus at GET /enroll/status in internal/controlplane/server.go) in Google OSS Agent Mesh (SAM) versions 0.1.0-alpha.1 through 0.1.0-alpha.8 allow an unauthenticated remote attacker to retrieve an approved bootstrap-enrolled peer's signed Biscuit identity token by supplying a peer_id obtainable from the unauthenticated GET /info endpoint. A related flaw in POST /enroll allowed any bootstrap-token holder to re-fetch another peer's credential. An attacker can replay the disclosed Biscuit token as a bearer credential on /policies to read mesh authorization policies and on /routers/lease to overwrite advertised router multiaddrs. Users should upgrade to version 0.1.0-alpha.9 or later, which requires cryptographic proof of possession of the enrollment private key on credential-releasing endpoints, enforces rate limiting, and validates router lease addresses.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-103090 since 09/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/22/2026).
Upgrading to version 0.1.0-alpha.9 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 0.1.0-alpha.0
- 0.1.0-alpha.1
- 0.1.0-alpha.2
- 0.1.0-alpha.3
- 0.1.0-alpha.4
- 0.1.0-alpha.5
- 0.1.0-alpha.6
- 0.1.0-alpha.7
- 0.1.0-alpha.8
License
Website
- Vendor: https://www.google.com/
- Product: https://github.com/google/sam/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing authenticationCWE: CWE-306 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: SAM 0.1.0-alpha.9
Timeline
09/30/2026 CVE reserved10/21/2026 VulDB entry created
10/22/2026 Advisory disclosed
10/22/2026 VulDB entry last update
Sources
Vendor: google.comProduct: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-103090 (🔒)
GCVE (CVE): GCVE-0-2026-103090
GCVE (VulDB): GCVE-100-425019
Entry
Created: 10/22/2026 00:36Changes: 10/22/2026 00:36 (70)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.