CVE-2026-110095: fast-uri vulnerable to improper path equivalence in relative reference normalization

Low CVSS 3.7

OSV id
GHSA-xhq7-xmqj-769h
Also known as
CVE-2026-110095
Published
Last modified

Affected packages

PackageAffected versionsFixed in
fast-uri
npm
< 2.4.8 2.4.8
fast-uri
npm
>= 3.0.0, < 3.1.9 3.1.9
fast-uri
npm
>= 4.0.0, < 4.2.3 4.2.3

Versions we track that it affects: fast-uri 3.1.5; fast-uri 3.1.5; fast-uri 3.1.5

How to fix it

fast-uri (npm)

Upgrade fast-uri to 2.4.8 or later.

npm install fast-uri@2.4.8
# if it is an indirect dependency: npm update fast-uri (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

fast-uri (npm)

Upgrade fast-uri to 3.1.9 or later.

npm install fast-uri@3.1.9
# if it is an indirect dependency: npm update fast-uri (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

fast-uri (npm)

Upgrade fast-uri to 4.2.3 or later.

npm install fast-uri@4.2.3
# if it is an indirect dependency: npm update fast-uri (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

Impact

fast-uri's normalize() and serialize() apply RFC 3986 dot-segment removal (remove_dot_segments) to the path of a relative-path reference. RFC 3986 section 5.2.4 defines that algorithm only for the merged target path during resolution, not for the reference itself, so applied to the reference it drops leading .. segments and can turn a document-relative reference into a root-relative one.

For example, normalize('a/../b') returns /b and normalize('../x') returns x, so resolve(base, normalize(ref)) points at a different resource than resolve(base, ref), and equal() treats distinct references as the same.

Applications that normalize attacker-supplied or user-supplied relative references and then resolve them, or use them as cache, deduplication, or authorization keys, can have a reference escape its intended directory and point at a different resource.

Patches

Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.

Workarounds

Do not normalize a relative reference before resolving it. Resolve it against the absolute base first, then normalize the absolute result.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.