---
title: "GHSA-jvvf-x445-j334: fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization"
description: "Moderate severity. fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization. Affects fast-uri; fixed in 4.1.5."
url: https://inlinr.com/advisories/GHSA-jvvf-x445-j334
lang: en
---

[Packages](https://inlinr.com/packages) / [fast-uri](https://inlinr.com/packages/fast-uri) / [Security](https://inlinr.com/packages/fast-uri/security)

Moderate Vulnerability GHSA-jvvf-x445-j334 CVE-2026-86818 Published 29 Sep 2026

# fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization

Your version 

Affected releases · [fast-uri](https://inlinr.com/packages/fast-uri)

- 4.x 4.1.3 – 4.1.4 Fixed in 4.1.5

On 4.x, the newest line:

```
npm install fast-uri@4.1.5
```

Every release on a timeline

1. Not affected

0.0.1 – 4.1.2  
40 releases
2. Affected

4.1.3 – 4.1.4  
2 releases
3. Fixed

4.1.5 – 4.2.3  
5 releases, latest

47 stable releases of fast-uri, oldest to newest.

## What happens

Impact

`fast-uri`'s `mailto` scheme parser compares each query field name to the reserved names (`to`, `subject`, `body`) while the name is still percent-encoded, and only percent-decodes it when storing it as a generic header. On serialize, the decoded name is re-emitted, so a field name such as `%74o` (percent-encoded `to`) is not recognized as a recipient at parse time (`parse().to` shows only the legitimate recipient) but materializes as a literal `to=` field after `serialize()`, and reparsing then treats it as a recipient. The same technique smuggles `subject` and `body` through `%73ubject` and `%62ody`.

An application that parses an untrusted mailto URI, makes a display, allowlist, or logging decision on `parse().to`, then re-serializes the result and passes the serialized string to a mail client or an outbound send path can gain an attacker-chosen recipient, subject, or body that was not visible when the recipient list was checked. A scanner inspecting the raw input for an extra `to=` sees nothing, because the injected field appears only after `fast-uri` serializes.

Patches

Upgrade to `fast-uri` 4.1.5.

Workarounds

Percent-decode and compare mailto field names case-insensitively before trusting `parse().to`, or re-check the recipient list on the serialized output rather than only on the initial parse, until upgrading.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: low
- **Integrity**: low
- **Availability**: none

CVSS:3.1/​AV:N/​AC:H/​PR:N/​UI:N/​S:U/​C:L/​I:L/​A:N

## References

- [Reference](https://github.com/fastify/fast-uri/security/advisories/GHSA-jvvf-x445-j334 "https://github.com/fastify/fast-uri/security/advisories/GHSA-jvvf-x445-j334")  
github.com/fastify/fast-uri/security/advisories…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-86818 "https://nvd.nist.gov/vuln/detail/CVE-2026-86818")  
nvd.nist.gov/vuln/detail/CVE-2026-86818
- [Fix commit](https://github.com/fastify/fast-uri/commit/f40a88f33e684a46faec3f5b820bcbb1e85add64 "https://github.com/fastify/fast-uri/commit/f40a88f33e684a46faec3f5b820bcbb1e85add64")  
f40a88f
- [Reference](https://cna.openjsf.org/security-advisories.html "https://cna.openjsf.org/security-advisories.html")  
cna.openjsf.org/security-advisories.html
- [Package](https://github.com/fastify/fast-uri "https://github.com/fastify/fast-uri")  
github.com/fastify/fast-uri
- [Reference](https://github.com/fastify/fast-uri/releases/tag/v4.1.5 "https://github.com/fastify/fast-uri/releases/tag/v4.1.5")  
github.com/fastify/fast-uri/releases/tag/v4.1.5

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
