# CVE-2026-7178: ChatGPTNextWeb NextChat Artifacts Endpoint route.ts storeUrl server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the NextChat Artifacts Endpoint to access internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-p35r-jg68-wccx

## What is CVE-2026-7178?

CVE-2026-7178 is a medium-severity server-side request forgery vulnerability in ChatGPTNextWeb NextChat, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in ChatGPTNextWeb NextChat up to 2.16.1. This affects the function storeUrl of the file app/api/artifacts/route.ts of the component Artifacts Endpoint. This manipulation of the argument ID causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-7178?

It affects 1 product.


Products: Nextchat Nextchat.

## How do I fix CVE-2026-7178?

No fix has been published for CVE-2026-7178 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7178 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7178 exists.

## Other vulnerabilities in ChatGPTNextWeb NextChat

- [CVE-2023-49785](https://insights.sbomify.com/CVE-2023-49785/): NextChat vulnerable to Server-Side Request Forgery and Cross-site Scripting (critical 9.1)
- [CVE-2025-50735](https://insights.sbomify.com/CVE-2025-50735/): Path traversal in n/a (high 7.5)
- [CVE-2026-7177](https://insights.sbomify.com/CVE-2026-7177/): ChatGPTNextWeb NextChat route.ts proxyHandler server-side request forgery (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7178 and fix it if it is affected.

What it is: CVE-2026-7178 is a medium-severity server-side request forgery vulnerability in ChatGPTNextWeb NextChat, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7178 exists.

Affected product: ChatGPTNextWeb NextChat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7178/ (Markdown: https://insights.sbomify.com/CVE-2026-7178/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7178
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7178
- OSV: https://osv.dev/vulnerability/CVE-2026-7178

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7178/
Summaries are generated and may contain mistakes; the official description above is the record.