Summary
Nango before 0.71.6 contains a missing authentication vulnerability in the runner's tRPC server. An unauthenticated attacker with network access to the runner port may invoke the exposed start procedure and execute arbitrary JavaScript within the runner process when the configured secret is not enforced.
Affected context
The vulnerability occurs in Nango deployments where the runner tRPC server is network-reachable and its start procedure is exposed without effective authentication. Risk is higher when the runner port is accessible from untrusted networks or when the RUNNER_SECRET_KEY control is configured but not actually enforced before request handling.
Exploit preconditions
- Attack surface: Network-accessible runner tRPC server
- Required access: No credentials; network connectivity to the runner port
- Trigger point: Invocation of the exposed
startprocedure - Why exploitation is possible: The procedure accepts requests without enforcing the expected runner secret, allowing unauthenticated code execution within the runner process
Why this happens
The underlying flaw is an authentication enforcement failure mapped to CWE-306: Missing Authentication for Critical Function. A privileged server procedure is reachable through a network interface, but the request path does not reliably verify caller identity or enforce the configured secret before performing its operation. This creates a trust boundary in which an unauthenticated caller can access functionality intended for authorized runner control.
Potential impact
- An attacker may execute arbitrary JavaScript within the runner process
- The affected runtime could be compromised
- Application secrets or connected service credentials could be exposed
- An attacker could modify workflows, data, or integration behavior
- The runner environment could be used for further network access or lateral movement
General mitigation guidance
Mitigation generally focuses on enforcing authentication and reducing exposure of privileged runner control interfaces.
Common defensive patterns include:
- Require authentication and authorization for every sensitive tRPC procedure
- Enforce the configured runner secret before dispatching or executing requests
- Bind the runner service to trusted interfaces and restrict access with network policy or firewall controls
- Apply least-privilege permissions to the runner process and its service credentials
- Separate administrative or execution endpoints from broadly reachable application traffic
- Fail closed when authentication configuration is absent, invalid, or unavailable
These patterns reduce the likelihood that network reachability alone grants access to code-execution functionality.
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis and code review checks for exposed procedures that lack authentication middleware
- Tests verifying that privileged endpoints reject unauthenticated and improperly authenticated requests
- Configuration-policy checks for runner ports exposed beyond trusted network segments
- Runtime monitoring for unexpected calls to runner control procedures
- Alerts for unusual JavaScript execution, process behavior, or outbound connections from runner instances
Automated application-security and API review tools may help identify routes or procedures whose authorization checks are missing or applied inconsistently.

