CVE-2026-44342: QuantumNous new-api · Cross-Site Request Forgery (CSRF)
Affects QuantumNous new-apiSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.12.0-alpha.1 when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.12.0-alpha.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade QuantumNous new-api to 0.12.0-alpha.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| QuantumNousnew-api | Affected
| Fixed in
|
GitHubquantumnous/new-apipkg:github/quantumnous/new-apiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade QuantumNous new-api to version 0.12.0-alpha.1 or later, where the vulnerability is fixed. Since this is a design flaw involving HTTP method usage for state-changing operations, applying the official fix is the recommended mitigation. No other vendor advisories or temporary fixes are provided.
Description
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 0.12.0-alpha.1, the email and WeChat account binding endpoints GET /api/oauth/email/bind and GET /api/oauth/wechat/bind used GET requests for state-changing account operations, allowing an attacker to trigger a logged-in user's browser to bind an attacker-controlled email address or OAuth identity in deployments where session cookies could be sent on cross-site navigations. This issue is fixed in version 0.12.0-alpha.1.