Missing RBAC check on Nango flow-read routes exposes production flows
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
Nango before 0.70.9 has two private flow-read routes that skip the RBAC authorization check on accounts with RBAC enabled. This missing authorization (CWE-862) lets a same-team user with the development_full_access role read production integration flow metadata and named flow configurations. An authenticated user with low privileges can reach data that guarded production routes deny, but tenant boundaries are not crossed.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
Nango is an open-source platform for connecting agents and products to third-party APIs. Prior to 0.70.9, on accounts with RBAC enabled through a plan with has_rbac=true, two private flow-read routes, GET /api/v1/integrations/:providerConfigKey/flows and GET /api/v1/flow/:flowName, apply webAuth but omit can({ action: 'read', resource: 'flow', scopedBy: envScope }). A same-team user with the development_full_access role can therefore request env=prod and read production integration flow metadata or named flow configuration despite being denied by guarded production routes. Both controllers use res.locals.environment from the authenticated account, so the issue bypasses the production role boundary but does not cross tenant boundaries. This issue is fixed in version 0.70.9 and managed-1.5.11-0.70.8-aae30d044d7e229807d51a3957c212f3fb689e1a
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Nango to version 0.70.9, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA nango (NangoHQ) Fixed in 0.70.9
Timeline
- 2026-10-12 Threatist record created from CVE-2026-102596
- 2026-10-14 CISA SSVC decision points changed
- 2026-10-14 Priority changed: LOW → MEDIUM
References
Other 5
- https://github.com/NangoHQ/nango/security/advisories/GHSA-vc5r-hj76-f35p
- https://github.com/NangoHQ/nango/pull/6603
- https://github.com/NangoHQ/nango/commit/3896f6abf71408b8966da1ea4afb1885647403c9
- https://github.com/NangoHQ/nango/releases/tag/managed-1.5.11-0.70.8-aae30d044d7e229807d51a3957c212f3fb689e1a
- https://github.com/NangoHQ/nango/releases/tag/v0.70.9
More NangoHQ vulnerabilities
- TI-2026-62543 Nango through 0.70.4 Server-Side Request Forgery via Configuration CVSS 4.0HIGH 7.1
- TI-2026-08178 Nango < 0.71.6 Missing Authentication RCE via runner tRPC server CVSS 4.0CRITICAL 9.2
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences