Quick answers
- Is CVE-2026-92804 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92804 being exploited in the wild.
- How severe is CVE-2026-92804?
- High severity, with a CVSS score of 7.1, published 16 September 2026.
- Which products and versions are affected?
- Nango through 0.70.4.
- Is there a fix for CVE-2026-92804?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92804 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92804?
- Check whether you run Nango at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Nango through version 0.70.4 fails to validate user-supplied connection configuration values before interpolating them into provider token and proxy URL templates, creating a server-side request forgery (SSRF) vulnerability. The vulnerable component is in the URL template interpolation logic (packages/shared/lib/utils/utils.ts). An authenticated attacker can supply crafted configuration values containing internal IP addresses or cloud metadata endpoints (e.g., 169.254.169.254) that get substituted into URLs, causing the server to make requests to unintended targets. This allows exfiltration of provider credentials or enumeration of internal services. A patch addressing input validation is expected in versions after 0.70.4.
Affected products
- Nango Nango through 0.70.4
Timeline
- 2026-09-16: disclosed