# CVE-2026-102596: Nango RBAC bypass on flow read routes

Source: https://junglewise.ai/threats/cve-2026-102596-nango-is-an-open-source-platform-for-connecting-agents-and  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-12. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-102596 · Severity: medium · CVSS 4.3 · Published 2026-10-12

Nango is an open-source platform that connects applications to third-party APIs. On accounts with role-based access control enabled, users with limited development access could bypass security controls to read production API integration configurations they should not see, potentially exposing sensitive connection metadata.

Technologies: [Nango](https://junglewise.ai/threats/technologies/nango). Vendors: [Nango](https://junglewise.ai/threats/vendors/nango).

## Quick answers

**Is CVE-2026-102596 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102596 being exploited in the wild.

**How severe is CVE-2026-102596?** Medium severity, with a CVSS score of 4.3, published 12 October 2026.

**Which products and versions are affected?** Nango before 0.70.9.

**Is there a fix for CVE-2026-102596?** Yes: fixed in 0.70.9, managed-1.5.11-0.70.8-aae30d044d7e229807d51a3957c212f3fb689e1a. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-102596 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-102596?** Check whether you run Nango at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 0.70.9, managed-1.5.11-0.70.8-aae30d044d7e229807d51a3957c212f3fb689e1a

## Technical details

Two API routes (GET /api/v1/integrations/:providerConfigKey/flows and GET /api/v1/flow/:flowName) applied web authentication but omitted the required RBAC guard for reading flow resources scoped by environment. A user with development_full_access role could craft requests with ?env=prod to read production flow metadata, bypassing the production role boundary without crossing tenant isolation.

## Affected products

- Nango Nango before 0.70.9

## Timeline

- 2026-10-12: advisory
- 2026-06-22: patched

## References

- [https://github.com/NangoHQ/nango/commit/3896f6abf71408b8966da1ea4afb1885647403c9](https://github.com/NangoHQ/nango/commit/3896f6abf71408b8966da1ea4afb1885647403c9)
- [https://github.com/NangoHQ/nango/pull/6603](https://github.com/NangoHQ/nango/pull/6603)

## Related threats

- [Nango orchestrator SQL injection via task group key](https://junglewise.ai/threats/cve-2026-125759-nango-before-0-71-3-contains-an-sql-injection-vulnerability-that)
- [Nango connection configuration SSRF in URL templates](https://junglewise.ai/threats/cve-2026-92804-nango-connection-configuration-ssrf-in-url-templates)
- [Nango missing authentication in runner tRPC server](https://junglewise.ai/threats/cve-2026-9317-nango-missing-authentication-in-runner-trpc-server)