Cross-origin API access via wildcard CORS headers
Published May 2, 2026 · Updated May 2, 2026
Permissive CORS in ChatGPTNextWeb NextChat 2.16.0 through 2.16.1 allows remote attackers to read API responses via malicious sites. The Next.js headers configuration assigns wildcard origins, methods, and request headers to every /api/* route, allowing cross-origin use of x-base-url to choose the proxy destination. Exploitation requires a user to visit attacker-controlled content and a non-static deployment; exposed responses can disclose configuration or server API keys.
Summary
What happened
Permissive CORS in ChatGPTNextWeb NextChat 2.16.0 through 2.16.1 allows remote attackers to read API responses via malicious sites. The Next.js headers configuration assigns wildcard origins, methods, and request headers to every /api/* route, allowing cross-origin use of x-base-url to choose the proxy destination. Exploitation requires a user to visit attacker-controlled content and a non-static deployment; exposed responses can disclose configuration or server API keys.
The record
- CVE
- CVE-2026-7643
- Published
- May 2, 2026
- Updated
- May 2, 2026
- Vendor
- ChatGPTNextWeb
- Product
- NextChat
- Classifications
- CWE-346, CWE-942, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2026CVE publishedPublication date reported by the CVE source.
- May 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.16.0
- Affected versionversion=2.16.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Permissive CORS Wildcard Policy on All API Endpoints Enabling Cross-Origin Exploitationproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo