CVE-2026-44342: Github.com/QuantumNous/new api New API Is Vulnerable To Vulnerability
MODERATECVE-2026-44342 is a MODERATE (CVSS 5.3) new api is vulnerable to vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Github.com/QuantumNous/new api libraries in the Go ecosystem. The issue involves new api is vulnerable to csrf through user email binding. Remediation is available by upgrading affected packages to version 0.12.0-alpha.1.
CVE-2026-44342 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-44342
To remediate this vulnerability, upgrade all affected Github.com/QuantumNous/new api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/QuantumNous/new-api to 0.12.0-alpha.1Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/QuantumNous/new-apiHow to Check if You Are Affected
To determine whether your application is affected by CVE-2026-44342, inspect your project dependencies for Github.com/QuantumNous/new api:
inspect dependencies for github.com/QuantumNous/new-apiAnalyze the terminal output to locate any version of Github.com/QuantumNous/new api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.12.0-alpha.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Github.com/QuantumNous/new api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-44342 Affected Github.com/QuantumNous/new api Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/QuantumNous/new-api
|
Go |
< 0.12.0-alpha.1
|
0.12.0-alpha.1
|
References
Frequently Asked Questions
What is CVE-2026-44342?
Which Github.com/QuantumNous/new api versions are affected?
What version fixes CVE-2026-44342?
Is github.com/QuantumNous/new-api affected?
What is the CVSS score of CVE-2026-44342?
What CWE is associated with CVE-2026-44342?
How can I check Go dependencies for CVE-2026-44342?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-26v7-h57m-gh9m",
"modified" : "2026-07-07T13:01:49Z",
"published" : "2026-07-07T13:01:49Z",
"aliases" : [ "CVE-2026-44342" ],
"summary" : "New API is vulnerable to CSRF through user email binding",
"details" : "## Summary\n\nThe 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.\n\nAffected endpoints included:\n\n- `GET /api/oauth/email/bind`\n- `GET /api/oauth/wechat/bind`\n\n## Impact\n\nA 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.\n\n## Affected versions\n\nVersions before `v0.12.0-alpha.1` are affected.\n\n## Patches\n\nThis 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.\n\n## Workarounds\n\nIf 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.\n\n## Resources\n\n- Fixed by commit `e099117c61391abdf888fb75e382a582e550bd0e`.\n- Relevant code paths: `router/api-router.go` and `controller/user.go`.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/QuantumNous/new-api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.12.0-alpha.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/QuantumNous/new-api/security/advisories/GHSA-26v7-h57m-gh9m"
}, {
"type" : "WEB",
"url" : "https://github.com/QuantumNous/new-api/commit/e099117c61391abdf888fb75e382a582e550bd0e"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/QuantumNous/new-api"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-352" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-07T13:01:49Z",
"nvd_published_at" : null
}
}