CVE-2026-44342: New API is vulnerable to CSRF through user email binding
Summary The email and WeChat account binding endpoints used GET requests for state-changing account operations. In deployments where session cookies could be sent on cross-site navigations, an attacker could trigger a logged-in user's browser to bind an attacker-controlled email address or OAuth identity.
Published Jul 7, 2026
Affected packages
github.com/QuantumNous/new-api
- Ecosystem
- Go
- Affected
- < 0.12.0-alpha.1
- Fixed in
- 0.12.0-alpha.1
- Check
go list -m github.com/QuantumNous/new-api
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The email and WeChat account binding endpoints used GET requests for state-changing account operations. In deployments where session cookies could be sent on cross-site navigations, an attacker could trigger a logged-in user's browser to bind an attacker-controlled email address or OAuth identity.
Affected endpoints included:
GET /api/oauth/email/bindGET /api/oauth/wechat/bind
Impact
A successful attack could change account binding state. For email binding, the attacker could bind an email address they control and then attempt follow-on account recovery flows. The default session cookie configuration uses SameSite=Strict, which mitigates common cross-site navigation attacks in modern browsers, so the issue is rated Medium.
Affected versions
Versions before v0.12.0-alpha.1 are affected.
Patches
This issue is fixed in v0.12.0-alpha.1. The fix changes email and WeChat binding routes from GET to POST and reads parameters from a JSON request body instead of query parameters. The same change set also normalizes password reset responses to avoid disclosing whether an email is registered.
Workarounds
If upgrading immediately is not possible, ensure session cookies are configured with strict SameSite behavior and block GET requests to /api/oauth/email/bind and /api/oauth/wechat/bind at the reverse proxy.
Resources
- Fixed by commit
e099117c61391abdf888fb75e382a582e550bd0e. - Relevant code paths:
router/api-router.goandcontroller/user.go.
Credited to kyo-w.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-64859
New API: User List API Leaks Root User Access Token Leading to Privilege Escalation
critical9.1Aug 17, 2026CVE-2026-64865
New API: Redis user quota cache overwrite via PUT /api/user/self allows quota bypass
medium6.0Aug 17, 2026CVE-2026-64866
New API: Admin can reset passkeys for same-level or higher-privileged users
medium5.1Aug 17, 2026CVE-2026-64868
New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging
high7.5Aug 17, 2026CVE-2026-71479
New API: Integer overflow in quota billing yields negative charges (self-crediting)
critical9.1Aug 17, 2026CVE-2026-33655
New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs
high7.7Jul 7, 2026
