New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 0.12.0-alpha.1, 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, allowing authenticated users to configure Webhook, Bark, or Gotify notification URLs that point at an internal or metadata IP address. This issue is fixed in version 0.12.0-alpha.1.
CVE-2026-33655
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EPSS
- 35.3%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Jul 9, 2026SSRF Protection Bypass via Unresolved Hostname in Notification URLs · Advisory · QuantumNous/new-api · GitHub
https://github.com/QuantumNous/new-api/security/advisories/GHSA-6qcr-qxgr-m7fvv0.12.0-alpha.1
Patch available: QuantumNous/new-api v0.12.0-alpha.1
https://github.com/QuantumNous/new-api/releases/tag/v0.12.0-alpha.1commit 20399d3c8fcb (QuantumNous/new-api)
Fix landed in QuantumNous/new-api commit 20399d3c8fcb — awaiting tagged release
https://github.com/QuantumNous/new-api/commit/20399d3c8fcb4e3649d53163eb11940fd6763743Vendor Advisories for CVE-2026-33655(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 16:10 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:51 UTCEG score recompute
- 2026-07-12 17:35 UTCEG score recompute
- 2026-07-12 06:18 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:00 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 07:45 UTCEG score recompute
- 2026-07-10 20:30 UTCEG score recompute
- 2026-07-10 09:14 UTCEG score recompute
- 2026-07-09 21:59 UTCEG score recompute
- 2026-07-09 10:43 UTCEG score recompute
- 2026-07-08 23:26 UTCEG score recompute
- 2026-07-08 12:11 UTCEG score recompute
- 2026-07-08 00:54 UTCEG score recompute
- 2026-07-07 13:38 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-33655?
When was CVE-2026-33655 disclosed?
Is CVE-2026-33655 actively exploited?
What is the CVSS score of CVE-2026-33655?
How do I remediate CVE-2026-33655?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33655
Is Your Infrastructure Affected by CVE-2026-33655?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.