CVE-2026-33655: New API SSRF Protection Bypass Vulnerability
HIGHCVE-2026-33655 is a HIGH (CVSS 7.7) ssrf protection bypass vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting New API libraries in the Go ecosystem. The issue involves ssrf protection bypass via unresolved hostname in notification urls. Remediation is available by upgrading affected packages to version 0.12.0-alpha.1.
CVE-2026-33655 at a Glance
Security Impact
CVSS: 7.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
How to Fix CVE-2026-33655
To remediate this vulnerability, upgrade all affected 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-33655, inspect your project dependencies for New API:
inspect dependencies for github.com/QuantumNous/new-apiAnalyze the terminal output to locate any version of 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-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In 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-33655 Affected 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-33655?
Which New API versions are affected?
What version fixes CVE-2026-33655?
Is github.com/QuantumNous/new-api affected?
What is the CVSS score of CVE-2026-33655?
What CWE is associated with CVE-2026-33655?
How can I check Go dependencies for CVE-2026-33655?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-6qcr-qxgr-m7fv",
"modified" : "2026-07-07T13:01:12Z",
"published" : "2026-07-07T13:01:12Z",
"aliases" : [ "CVE-2026-33655" ],
"summary" : "New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs",
"details" : "## Summary\n\nThe default SSRF protection configuration did not apply IP filtering to hostnames. With `ApplyIPFilterForDomain` disabled by default, URL validation checked domain allow/block rules but did not resolve a hostname and validate the resolved IP address. Authenticated users could configure notification URLs for Webhook, Bark, or Gotify notifications and point a hostname at an internal or metadata IP address.\n\n## Impact\n\nA regular authenticated user could cause the server to send notification requests to internal HTTP services reachable from the deployment network. Depending on the target environment, this could expose sensitive internal data through timing, errors, or response-dependent behavior. The issue is rated High.\n\n## Affected versions\n\nVersions before `v0.12.0-alpha.1` are affected. The previous affected range of `<= v0.11.4-alpha.4` was too narrow because the unsafe default remained present until the `v0.12.0-alpha.1` fix.\n\n## Patches\n\nThis issue is fixed in `v0.12.0-alpha.1`. The default fetch setting now sets `ApplyIPFilterForDomain: true`, causing hostname destinations to be resolved and checked against the configured IP filtering rules during URL validation.\n\nThis patch addresses the unresolved-hostname bypass for the affected notification URL paths. It does not mark the separate DNS rebinding advisory as fixed, because connection-time IP enforcement is tracked separately.\n\n## Workarounds\n\nIf upgrading immediately is not possible, explicitly enable `ApplyIPFilterForDomain`, restrict notification URL domains with an allowlist, disable user-configurable notification URLs where practical, and enforce outbound network filtering at the host or network layer.\n\n## Resources\n\n- Fixed by commit `20399d3c8fcb4e3649d53163eb11940fd6763743`.\n- Relevant code paths: `setting/system_setting/fetch_setting.go`, `common/ssrf_protection.go`, `service/webhook.go`, and `service/user_notify.go`.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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-6qcr-qxgr-m7fv"
}, {
"type" : "WEB",
"url" : "https://github.com/QuantumNous/new-api/commit/20399d3c8fcb4e3649d53163eb11940fd6763743"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/QuantumNous/new-api"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-07T13:01:12Z",
"nvd_published_at" : null
}
}