Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-9317 – Unauthenticated Remote Code Execution – Nango < 0.71.6

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-9317 is a missing authentication vulnerability in Nango’s runner tRPC server that allows unauthenticated attackers to execute arbitrary JavaScript code within the runner process. It affects all Nango versions prior to 0.71.6 and carries a CVSS v4.0 base score of 9.2 (Critical), reflecting network exploitability with no authentication or user interaction required.

Technical details

  • Root cause: the runner tRPC server exposes a "start" procedure without enforcing authentication; the RUNNER_SECRET_KEY environment variable intended to protect it is not actually validated.
  • Trigger condition: an attacker only needs network access to the runner port to invoke the exposed start procedure directly.
  • Attack vector: network-based, no privileges or user interaction required (CWE-306: Missing Authentication for Critical Function).
  • Impact: remote code execution — arbitrary JavaScript is executed within the runner process, which handles integration/connector logic, potentially compromising confidentiality, integrity, and availability of the runner and any credentials/data it processes.

Affected software

  • NangoHQ Nango: all versions prior to 0.71.6

Severity

  • CVSS v4.0: 9.2 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 8.1 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade Nango to version 0.71.6 or later, which enforces authentication on the affected tRPC procedures.
  • If patching is not immediately feasible: restrict network access to the runner port to trusted internal subnets hosting the main Nango application only, apply strict firewall rules, and ensure no public-facing load balancer exposes the runner port; audit environment variable enforcement to confirm RUNNER_SECRET_KEY (or its successor controls) is properly validated.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named response header access-control-expose-headers: X-Nango-Signature
  • Named <meta> tag content (nango-env-hash): any non-empty value

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge