New API 0.11.9 Alpha 1
Approved changes feed: RSS · Atom
cpe:2.3:a:newapi:new_api:0.11.9:alpha1:*:*:*:*:*:*part: a version: 0.11.9 update: alpha1
| Vendor | Newapi (6e38d999-40be-58a3-bf1f-b693e7f7fa9d) |
|---|---|
| Product | New Api (4d563535-ddf4-5b5c-bac8-09df55ef751a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/quantumnous/new-api |
purl2cpe | 2026-07-28 16:40:52.941687 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42339 |
vulnerable | 2026-06-08 08:03:16.181385 |
New API: SSRF Filter Bypass via 0.0.0.0
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. In versions 0.11.9-alpha.1 and prior, the SSRF protection introduced in v0.9.0.5 (CVE-2025-59146) and hardened in v0.9.6 (CVE-2025-62155) does not block the unspecified address 0.0.0.0. A regular (non-admin) user holding any valid API token can send a multimodal request to /v1/chat/completions, /v1/responses, or /v1/messages with 0.0.0.0 as the image/file URL host, bypassing the private-IP filter and causing the server to issue HTTP requests to localhost. This constitutes at minimum a blind SSRF; when the request is routed through an AWS/Bedrock Claude adaptor, the fetched content is inlined into the model response, upgrading it to a full-read SSRF. At time of publication, there are no publicly available patches.
Published: 2026-05-08T22:21:53.902Z
Updated: 2026-05-11T15:56:48.213Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-32879 |
vulnerable | 2026-06-08 07:57:18.285908 |
New API has passkey-based secure step-up verification bypass for root-only channel secret disclosure
MEDIUM (4.9)
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Starting in version 0.10.0, a logic flaw in the universal secure verification flow allows an authenticated user with a registered passkey to satisfy secure verification without completing a WebAuthn assertion. As of time of publication, no known patched versions are available. Until a patched release is applied, do not rely on passkey as the step-up method for privileged secure-verification actions; require TOTP/2FA for those actions where operationally possible; or temporarily restrict access to affected secure-verification-protected endpoints.
Published: 2026-03-23T19:24:16.336Z
Updated: 2026-03-24T15:13:22.246Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.