{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7178 exists.","fix":"No fix has been published for CVE-2026-7178 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-7178 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7178 exists.\n\nAffected product: ChatGPTNextWeb NextChat. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7178/ (Markdown: https://insights.sbomify.com/CVE-2026-7178/index.md)","id":"CVE-2026-7178","markdown":"https://insights.sbomify.com/CVE-2026-7178/index.md","name":"CVE-2026-7178","record":{"aliases":["GHSA-p35r-jg68-wccx"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NextChat web application","requires_auth":"none","summary":"Remote attackers can exploit a server-side request forgery vulnerability in the NextChat Artifacts Endpoint to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"nextchat","vendor":"nextchat"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"ChatGPTNextWeb NextChat Artifacts Endpoint route.ts storeUrl server-side request forgery","id":"CVE-2026-7178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"OSPG binwalk WinCE Extraction Plugin winceextract.py read_null_terminated_string path traversal","id":"CVE-2026-7179"},"packages":[],"prev":{"headline":"ChatGPTNextWeb NextChat route.ts proxyHandler server-side request forgery","id":"CVE-2026-7177"},"products":["NextChat"],"published":"2026-04-27","related":[{"cvss_score":9.1,"headline":"NextChat vulnerable to Server-Side Request Forgery and Cross-site Scripting","id":"CVE-2023-49785","kev_date_added":null,"published":"2024-03-11"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2025-50735","kev_date_added":null,"published":"2025-11-03"},{"cvss_score":6.9,"headline":"ChatGPTNextWeb NextChat route.ts proxyHandler server-side request forgery","id":"CVE-2026-7177","kev_date_added":null,"published":"2026-04-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["ChatGPTNextWeb"]},"summary":"Remote attackers can exploit a server-side request forgery vulnerability in the NextChat Artifacts Endpoint to access internal resources.","url":"https://insights.sbomify.com/CVE-2026-7178/"}