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-2026-125759
HIGHPre-NVD 7.57.5ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-121242 (ENISA EUVD) · GHSA-3w4f-3q27-257j (GitHub Security Advisories)Source: ENISA EUVD
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 50EG Risk 50/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.3%
- EPSS %ILE
- 23rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 10, 2026
Last Modified
November 13, 2026
Advisory Details (6)
Auto-updated Nov 10, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
Web page
Nango before 0.71.3 SQL Injection via Orchestrator Task Group Key | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nango-before-0.71.3-sql-injection-via-orchestrator-task-group-keyWeb page
nango/packages/orchestrator/lib/events.ts at v0.71.1 · NangoHQ/nango · GitHub
https://github.com/NangoHQ/nango/blob/v0.71.1/packages/orchestrator/lib/events.ts#L162GitHub release Patch Available
v0.71.3
Patch available: NangoHQ/nango v0.71.3
https://github.com/NangoHQ/nango/releases/tag/v0.71.3GitHub pull request Patch Available
fix(orchestrator): change NOTIFY to use parameterized pg_notify
Patch available: NangoHQ/nango v0.71.3 (PR #6867 merged 2026-07-22)
https://github.com/NangoHQ/nango/pull/6867GitHub commit Patch Available
commit 83f24a5a1ed2 (NangoHQ/nango)
Patch available: NangoHQ/nango v0.71.3 (contains commit 83f24a5a1ed2)
https://github.com/NangoHQ/nango/commit/83f24a5a1ed2db59b6d472e49c25333dc6f28709GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Unauthenticated SQL injection in the task orchestrator via Postgres NOTIFY (attacker-controlled group key) · Advisory · NangoHQ/nango · GitHub
https://github.com/NangoHQ/nango/security/advisories/GHSA-8m28-9wcj-v8wwVendor Advisories for CVE-2026-125759(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-11-13 16:50 UTCEchelonGraph re-scored
- 2026-11-13 16:50 UTCGHSA enrichmentGHSA-3w4f-3q27-257j · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-13 15:42 UTCEchelonGraph re-scored
- 2026-11-13 15:42 UTCGHSA enrichmentGHSA-3w4f-3q27-257j · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-13 15:27 UTCEchelonGraph re-scored
- 2026-11-13 15:27 UTCGHSA enrichmentGHSA-3w4f-3q27-257j · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-11-11 03:52 UTCGHSA enrichmentGHSA-3w4f-3q27-257j · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-10 18:54 UTCEchelonGraph re-scored
- 2026-11-10 18:54 UTCGHSA enrichmentGHSA-3w4f-3q27-257j · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-10 16:29 UTCEchelonGraph re-scored
- 2026-11-10 16:00 UTCENISA EUVD ID recordedEUVD-2026-121242 · Source: ENISA EUVD
- 2026-11-10 15:31 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
- 2026-11-10 15:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-125759?
CVE-2026-125759 is a high-severity vulnerability; its CVE record was published on November 10, 2026. 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…
When was CVE-2026-125759 made public?
CVE-2026-125759 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 10, 2026. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-125759 actively exploited?
CVE-2026-125759 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-125759?
CVE-2026-125759 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-125759?
A fix for CVE-2026-125759 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-125759 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-125759
Is Your Infrastructure Affected by CVE-2026-125759?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.