[From nobody Sat Oct 24 16:37:05 2026
Received: (at submit) by bugs.debian.org; 24 Oct 2026 07:17:09 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-107.4 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
 FOURLA,FROMDEVELOPER,SPF_HELO_NONE,SPF_PASS,USER_IN_DKIM_WELCOMELIST
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 25; hammy, 150; neutral, 186; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;carnil@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:34614)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xKW06-00H61s-0S
 for submit@bugs.debian.org; Sat, 24 Oct 2026 07:17:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=ZhNGPvD+jW3/z9RfiJ2Tls2tNHXAe4jsO8z9pRcExyk=; b=e531YhRjEPYOwFenQbwwtn2vmx
 p/5tjWh17BMraMfFn/1VxHA5Eo4MvrlUgqJFaAxdu0jRExE6bjAufzaP5XMYxPbVScclocbeC875j
 DoeljvQVJKpUSzqNTXuJiyQlVDqvPX8m+SDaW84Tl5reNx6xO0ANIslcvZogStUqD9E2nVQFwr8XC
 Muvwjd23+nF7mvPBBlISFAB0T800/Okwz3pKPs8JoGb/M83nIttSRJqELbMiijFxvUHQXRq/pT2pz
 H4wbZ/jw3XjlkuXHgs+qJ6NBApD/AiJrGfM4kePYbvy2F8OWvP5n+21laPZ1wnXsggmkfJ0tW6ZWl
 /26aOpvw==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xKW03-003o7s-0u
 for submit@bugs.debian.org; Sat, 24 Oct 2026 07:17:08 +0000
Received: by eldamar.lan (Postfix, from userid 1000)
 id 72763DC07B8; Sat, 24 Oct 2026 09:17:06 +0200 (CEST)
Date: Sat, 24 Oct 2026 09:17:06 +0200
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: submit@bugs.debian.org
Subject: node-ajv: CVE-2026-110180 CVE-2026-110306 CVE-2026-110725
Message-ID: &lt;atxbco_qvy6QTubF@eldamar.lan&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: carnil
Delivered-To: submit@bugs.debian.org

Source: node-ajv
Version: 8.20.0~ds+~cs7.1.6-2
X-Debbugs-CC: team@security.debian.org
Severity: important
Tags: security upstream

Hi,

The following vulnerabilities were published for node-ajv.

CVE-2026-110180[0]:
| fast-uri is a dependency-free RFC 3986 URI parser and serializer for
| Node.js. In versions from 2.4.2 through 2.4.7, from 3.1.3 through
| 3.1.8, and from 4.0.1 through 4.2.2, for HTTP-family schemes the
| canonicalizeHost() function passes the parsed host to the WHATWG URL
| parser and adopts its hostname without checking that the parser
| consumed the entire input as a host, so the authority can be
| silently rewritten: data before an at-sign is dropped and tab,
| carriage-return, and line-feed characters are stripped, with no
| error reported. An application that enforces host-based policy such
| as denylists, loopback filtering, redirect validation, or outbound
| proxy routing on one representation can then see the canonical host
| diverge from what it checked, allowing traffic to be steered to an
| unintended destination. The issue is fixed in fast-uri 2.4.8, 3.1.9,
| and 4.2.3, and users should upgrade to one of these versions or
| later. As a workaround, reject an authority that contains more than
| one at-sign or any tab, carriage-return, or line-feed before calling
| fast-uri, or treat any non-empty parse error as fatal and compare
| hosts only from the same parse result.


CVE-2026-110306[1]:
| fast-uri is a dependency-free RFC 3986 URI parser and serializer for
| Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and
| from 4.0.0 through 4.2.2, fast-uri percent-decodes the scheme
| component with the legacy global unescape() function before
| validating it, so an input whose decoded scheme is a dangerous token
| is emitted as a live scheme even though RFC 3986 does not allow
| percent-encoding in a scheme and no other parser accepts it. An
| application that screens dangerous schemes on the raw input and then
| stores or renders the normalized or resolved result can turn an
| inert string into an executable javascript, data, or vbscript URL,
| producing a stored or reflected cross-site scripting vector, and the
| equal() comparison treats an encoded and a plain scheme as the same,
| which can bypass equality-based allowlists. The issue is fixed in
| fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of
| these versions or later. As a workaround, reject input whose scheme
| part contains a percent sign, or check the parsed scheme against an
| allowlist after normalization and use that same parsed result rather
| than the raw string.


CVE-2026-110725[2]:
| fast-uri is a dependency-free RFC 3986 URI parser and serializer for
| Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and
| from 4.0.0 through 4.2.2, when serialize(), normalize(), or
| resolve() are called with the non-default option reference set to
| suffix on a reference that has no authority, the emitted relative
| reference can contain a bare colon in its first path segment without
| escaping it, even though RFC 3986 forbids that because it makes the
| string reparse as an absolute URI with a scheme. An application that
| serializes or normalizes a relative reference with the suffix option
| and then treats the result as a URI can turn inert input into a live
| javascript, data, or vbscript URL, a cross-site scripting vector,
| and the equal() comparison can conflate a scheme-bearing reference
| with a relative one. Exposure is limited to applications using the
| non-default suffix reference option. The issue is fixed in fast-uri
| 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these
| versions or later. As a workaround, avoid the suffix reference
| option on untrusted input, or percent-encode a colon in the first
| path segment of the result before treating it as a URI.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-110180
    https://www.cve.org/CVERecord?id=CVE-2026-110180
[1] https://security-tracker.debian.org/tracker/CVE-2026-110306
    https://www.cve.org/CVERecord?id=CVE-2026-110306
[2] https://security-tracker.debian.org/tracker/CVE-2026-110725
    https://www.cve.org/CVERecord?id=CVE-2026-110725

Regards,
Salvatore
]