CVE-2026-33655: QuantumNous New API SSRF via unresolved hostnames in notifications

CVE-2026-33655 · Severity: high · CVSS 7.7 · Published 2026-07-09

New API, a management system for AI assets and language models, contains a security flaw that allows users to bypass internal network protections. By providing a specially crafted web address for notifications, an authenticated user can force the system to connect to internal servers or cloud metadata services that should be private. This could lead to the exposure of sensitive internal data or unauthorized access to other systems within the corporate network.

Technologies: github.com/QuantumNous/new-api (Go), QuantumNous New API. Vendors: Go, QuantumNous.

Quick answers

Is CVE-2026-33655 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33655 being exploited in the wild.
How severe is CVE-2026-33655?
High severity, with a CVSS score of 7.7, published 9 July 2026.
Which products and versions are affected?
github.com/QuantumNous/new-api (Go) < 0.12.0-alpha.1, SEMVER:introduced=0,fixed=0.12.0-alpha.1; QuantumNous New API < 0.12.0-alpha.1.
Is there a fix for CVE-2026-33655?
Yes. github.com/QuantumNous/new-api (Go): upgrade to 0.12.0-alpha.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33655 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-33655?
Check whether you run github.com/QuantumNous/new-api (Go) or QuantumNous New API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/QuantumNous/new-api (Go): upgrade to 0.12.0-alpha.1 or later
    go get github.com/QuantumNous/new-api@v0.12.0-alpha.1

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in QuantumNous New API prior to version 0.12.0-alpha.1. The root cause is a flaw in the URL validation logic where the 'ApplyIPFilterForDomain' setting was disabled by default. While the system checked domain allow/block lists, it did not resolve hostnames to their underlying IP addresses before making requests. This allows an authenticated attacker to configure notification URLs (such as Webhook, Bark, or Gotify) that point to internal IP addresses or cloud metadata services (e.g., 169.254.169.254). An attacker can exploit this to probe internal network services and potentially exfiltrate sensitive data. The issue is addressed in version 0.12.0-alpha.1 by enabling IP filtering for domains by default and hardening validation in the 'VideoProxy' and 'RelayMidjourneyImage' endpoints.

Affected products

  • QuantumNous new-api < 0.12.0-alpha.1

Identifiers

  • CVE-2026-33655
  • GHSA-6qcr-qxgr-m7fv
  • GO-2026-5930

Timeline

  • 2026-03-31: patched: Fix committed and version 0.12.0-alpha.1 released.
  • 2026-07-03: advisory: GitHub Security Advisory GHSA-6qcr-qxgr-m7fv published.
  • 2026-07-09: disclosed: CVE-2026-33655 published to NVD.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.