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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.71.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions are Nango before the fix commit 83f24a5a1ed2db59b6d472e49c25333dc6f28709 (VulnCheck lists nango before 0.71.3). Affects 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.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions are Nango before the fix commit 83f24a5a1ed2db59b6d472e49c25333dc6f28709 (VulnCheck lists nango before 0.71.3). Affects 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.Upgrade to a fixed version: 0.71.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- NangoHQ nango
fixed in 0.71.3
Evidence 8
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125759
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: cve.now feed data
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: github.com, vulncheck.com
Which versions are affected by CVE-2026-125759?
nango: before 0.71.3.Source: cve.now feed data
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: github.com, vulncheck.com
How do I fix CVE-2026-125759?
Upgrade Nango to 0.71.3 or later, which contains the fix.Source: github.com, vulncheck.com
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: github.com, vulncheck.com