CVE-2026-9317
No exploitation reported by the sources we read.
- Published2026-09-04
- WeaknessCWE-306
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Nango before 0.71.6 contains a missing authentication vulnerability in the runner tRPC server that allows unauthenticated attackers to execute arbitrary JavaScript code by invoking the exposed start procedure without credentials. Attackers with network access to the runner port can send requests to the unauthenticated start procedure, bypassing the unenforced RUNNER_SECRET_KEY environment variable, to achieve remote code execution within the runner process.
Timeline
dates in UTC- 2026-09-0418:18CVE publishedNVD
Versions per branch
Products declared by the CNA
As VulnCheck, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- NangoHQ nangoother versions: not affected
https://github.com/NangoHQ/nango
Affected- < 0.71.6fixed in 0.71.6semver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-05
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-9317 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-09-08
- CNACVSS 4.09.2known since 2026-10-23
- CNACVSS 3.18.1known since 2026-10-23
- CNAweakness (CWE)CWE-306known since 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-11-18
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-71631same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-9cph-w8mv-q56rsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-09-04
- Last Modified
- 2026-09-23
- NVD status
- Deferred
- GitHub Advisory
- GHSA-9cph-w8mv-q56r
Frequently asked questions
What is CVE-2026-9317?
Is CVE-2026-9317 actively exploited?
What is the CVSS score for CVE-2026-9317?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-9cph-w8mv-q56r
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- CISA Vulnrichment · CC0-1.0