Quick answers
- Is CVE-2026-7178 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7178 being exploited in the wild.
- How severe is CVE-2026-7178?
- High severity, with a CVSS score of 7.3, published 27 April 2026.
- Which products and versions are affected?
- ChatGPTNextWeb NextChat <= 2.16.1.
- Is there a fix for CVE-2026-7178?
- 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-7178 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-7178?
- Check whether anything you run is named in the advisory. 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
A Server-Side Request Forgery (SSRF) vulnerability exists in the `app/api/artifacts/route.ts` endpoint of NextChat. The application takes an unvalidated `id` query parameter and concatenates it into a backend fetch request targeting the Cloudflare KV API. Because the fetch API performs URL path normalization, an attacker can provide directory traversal sequences (e.g., `../../`) to escape the intended KV namespace and reach the Cloudflare API root. Since the server automatically attaches the `CLOUDFLARE_KV_API_KEY` to these requests, an attacker can invoke arbitrary Cloudflare API functions with the server's privileges. This vulnerability is exploitable remotely without authentication. As of the advisory date, no official patch has been confirmed by the maintainers.
Affected products
- ChatGPTNextWeb NextChat <= 2.16.1
Timeline
- 2026-04-06: other: Vulnerability discovered and documented in private gist
- 2026-04-27: disclosed: Public disclosure of CVE-2026-7178
- 2026-04-27: advisory: VulDB entry published