CVE-2026-108716

mcp-remote 0.8.0 through 0.14.3 Cleartext Credential Transmission via --device-code OAuth Grant

Published Oct 11, 2026 CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
Description
mcp-remote 0.8.0 through 0.14.3 contains a cleartext transmission vulnerability in authorizeWithDeviceCode that sends client secrets and receives tokens without enforcing HTTPS endpoints. When discovered device authorization and token endpoints are non-loopback http URLs, on-path network attackers can capture the client secret plus issued access and refresh tokens.

Analysis

AI-generated

Technical impact

The vulnerability allows a device authorization component to send client secrets and receive access tokens without enforcing HTTPS. The transmitted credentials and tokens are therefore exposed in cleartext and can be captured by an on‑path network attacker. The exposed information permits full impersonation of the client and continued use of any authorized resources. The weakness is classified under CWE‑319.

Affected Systems

Vendor punkpeye’s mcp‑remote product, versions 0.8.0 through 0.14.3, is affected. No specific sub‑product or build is excluded; the entire range of these releases shares the same insecure implementation.

Risk and Exploitability

The CVSS score of 6 indicates a severity vulnerability. No EPSS score is published, so the likelihood of exploitation is not quantified, and the issue is not listed in the CISA KEV catalog. An attacker with access to the network path that hosts the device‑authorization and token endpoints, provided they are non‑loopback HTTP URLs, can capture the client secret, access token, and refresh token. Remote attackers with such network access could therefore acquire the credentials to compromise the application’s authentication flow.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade mcp‑remote to a version newer than 0.14.3 where the device‑authorization path enforces HTTPS.
  • Configure all device‑authorization and token endpoints to use HTTPS so that credential transit is protected.
  • Restrict the device‑authorization endpoints to a loopback or otherwise confined network segment, and enforce firewall rules that block unauthenticated external HTTP traffic to those endpoints.

Generated by OpenCVE AI on October 11, 2026 at 13:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Punkpeye
Punkpeye mcp-remote
Vendors & Products Punkpeye
Punkpeye mcp-remote
Type Values Removed Values Added
Description mcp-remote 0.8.0 through 0.14.3 contains a cleartext transmission vulnerability in authorizeWithDeviceCode that sends client secrets and receives tokens without enforcing HTTPS endpoints. When discovered device authorization and token endpoints are non-loopback http URLs, on-path network attackers can capture the client secret plus issued access and refresh tokens.
Title mcp-remote 0.8.0 through 0.14.3 Cleartext Credential Transmission via --device-code OAuth Grant
Weaknesses CWE-319
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-319

    Cleartext Transmission of Sensitive Information

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 13, 2026, 5:01 PM
Reserved
Oct 11, 2026, 1:51 AM
Status
Deferred
Published
Oct 11, 2026, 1:17 PM
Modified
Oct 16, 2026, 7:18 PM