Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 14 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 13 Oct 2026 04:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nangohq
Nangohq nango |
|
| Vendors & Products |
Nangohq
Nangohq nango |
Mon, 12 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 | |
| Title | Nango: Production flow RBAC bypass on private flow-read routes | |
| Weaknesses | CWE-862 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-14T11:49:26.276Z
Reserved: 2026-09-29T14:18:02.920Z
Link: CVE-2026-102596
Updated: 2026-10-14T11:49:05.307Z
Status : Deferred
Published: 2026-10-12T22:17:02.960
Modified: 2026-10-14T12:17:17.070
Link: CVE-2026-102596
No data.
OpenCVE Enrichment
Updated: 2026-10-13T04:30:17Z