CVE-2026-9317
Received Received - Intake

Authentication Bypass in Nango Runner Leads to RCE

Vulnerability report for CVE-2026-9317, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: VulnCheck

Description

Nango before 0.71.6 contains a missing authentication vulnerability in the runner tRPC server that allows unauthenticated attackers to execute arbitrary JavaScript code by invoking the exposed start procedure without credentials. Attackers with network access to the runner port can send requests to the unauthenticated start procedure, bypassing the unenforced RUNNER_SECRET_KEY environment variable, to achieve remote code execution within the runner process.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-05
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nango nango to 0.71.6 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Nango before version 0.71.6 has a missing authentication vulnerability in its runner tRPC server. This flaw allows unauthenticated attackers to execute arbitrary JavaScript code by calling the exposed start procedure without providing credentials. The vulnerability exists because the RUNNER_SECRET_KEY environment variable is not enforced, enabling attackers with network access to the runner port to send requests and achieve remote code execution within the runner process.

Detection Guidance

Check if the Nango runner tRPC server is exposed on the network without authentication. Look for open ports where the runner service is running. Inspect network traffic for requests to the unauthenticated start procedure. Verify if the RUNNER_SECRET_KEY environment variable is missing or unenforced.

Impact Analysis

If you use Nango before 0.71.6, attackers could gain control of your runner process, allowing them to run malicious JavaScript code on your system. This could lead to unauthorized access, data theft, or further compromise of your infrastructure. The impact depends on the privileges of the runner process and the sensitivity of the data it handles.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, which may violate GDPR, HIPAA, or other regulations. GDPR requires protecting personal data, while HIPAA mandates safeguarding protected health information. A successful exploit could result in non-compliance, legal penalties, or reputational damage due to compromised sensitive data.

Mitigation Strategies

Upgrade Nango to version 0.71.6 or later to address the missing authentication flaw. Ensure the RUNNER_SECRET_KEY environment variable is properly set and enforced. Restrict network access to the runner port to trusted sources only. Monitor for unauthorized access attempts or suspicious activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9317. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart