https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T08:43:43.043981+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-335587 EUVD-2026-335587 2026-10-06T08:43:43.089185+00:00 EUVD-2026-335587 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33655 fkie_cve-2026-33655 2026-10-06T08:43:43.089223+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-6qcr-qxgr-m7fv GHSA-6qcr-qxgr-m7fv — New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs 2026-10-06T08:43:43.089259+00:00

Affected: Go: github.com/QuantumNous/new-api

## 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 `Appl…