Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-33655 high CVSS 7.7

SSRF (Server-Side Request Forgery) in github.com/QuantumNous/new-api (CVE-2026-33655)

Summary

SSRF in github.com/QuantumNous/new-api (CVE-2026-33655). Confidential information can be exposed externally. Exploitable via ApplyIPFilterForDomain. Mitigation: upgrade to 0.12.0-alpha.1 or later.

Original description

The description as published by the source.

Summary

The 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.

Impact

A 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.

Affected versions

Versions 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.

Patches

This 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.

This 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.

Workarounds

If upgrading immediately is not possible, explicitly enable `Apply…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-33655 has been found in github.com/QuantumNous/new-api.
Attackers can target a specific entry point like ApplyIPFilterForDomain over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/QuantumNous/new-api to 0.12.0-alpha.1 or later.
If unsure, ask your IT team or search "github.com/QuantumNous/new-api CVE-2026-33655" on the vendor's site.

CVE-2026-33655 (github.com/QuantumNous/new-api) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ApplyIPFilterForDomain
Patched: 0.12.0-alpha.1 — apply immediately
Workaround: If 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
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in github.com/QuantumNous/new-api. Attackers reach the vulnerable code path via ApplyIPFilterForDomain.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/QuantumNous/new-api. Attack surface: ApplyIPFilterForDomain.

🔥 Severity

Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.12.0-alpha.1.

🛡️ Workaround

Workaround: If 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

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/QuantumNous/new-api' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/QuantumNous/new-api' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/QuantumNous/new-api を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    If 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

    パッチが適用されるまでの応急処置として、If 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 を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/QuantumNous/new-api to 0.12.0-alpha.1

    ステージング環境で 0.12.0-alpha.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/QuantumNous/new-api
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.12.0-alpha.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details