ubuntu-cve-2026-84292
Vulnerability from osv_ubuntu
fast-uri serializes the port component of a URI without validating it. When recomposing the authority, the userinfo and host components are escaped but the port is concatenated verbatim, so a port value that is not a sequence of digits can inject authority delimiters, demoting the intended host to userinfo and pointing the authority at an attacker-controlled host. Both fast-uri and Node's URL read the result back as the attacker's host with no error, so re-validating the built URI does not catch it. This affects applications that build URIs from parts and assign untrusted data to the port component through the serialize, normalize, or equal functions in their object forms. The issue affects fast-uri versions before 2.4.6, from 3.0.0 before 3.1.7, and from 4.0.0 before 4.1.4. It is fixed in 2.4.6, 3.1.7, and 4.1.4, where recomposeAuthority rejects any port that is not a digit sequence per RFC 3986.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-ajv",
"binary_version": "5.0.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "node-ajv",
"purl": "pkg:deb/ubuntu/node-ajv@5.0.0-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-ajv",
"binary_version": "6.10.2-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "node-ajv",
"purl": "pkg:deb/ubuntu/node-ajv@6.10.2-1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.10.2-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-ajv",
"binary_version": "6.12.6-3"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "node-ajv",
"purl": "pkg:deb/ubuntu/node-ajv@6.12.6-3?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.12.6-2",
"6.12.6-3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-ajv",
"binary_version": "8.12.0~ds+~2.1.1-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "node-ajv",
"purl": "pkg:deb/ubuntu/node-ajv@8.12.0~ds+~2.1.1-4?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.12.6-3",
"8.12.0~ds+~2.1.1-4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-ajv",
"binary_version": "8.17.1~ds+~3.0.1+~3.1.0-4build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "node-ajv",
"purl": "pkg:deb/ubuntu/node-ajv@8.17.1~ds+~3.0.1+~3.1.0-4build1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"8.12.0~ds+~2.1.1-5",
"8.17.1~ds+~3.0.1+~3.1.0-2",
"8.17.1~ds+~3.0.1+~3.1.0-4build1"
]
}
],
"aliases": [],
"details": "fast-uri serializes the port component of a URI without validating it. When recomposing the authority, the userinfo and host components are escaped but the port is concatenated verbatim, so a port value that is not a sequence of digits can inject authority delimiters, demoting the intended host to userinfo and pointing the authority at an attacker-controlled host. Both fast-uri and Node\u0027s URL read the result back as the attacker\u0027s host with no error, so re-validating the built URI does not catch it. This affects applications that build URIs from parts and assign untrusted data to the port component through the serialize, normalize, or equal functions in their object forms. The issue affects fast-uri versions before 2.4.6, from 3.0.0 before 3.1.7, and from 4.0.0 before 4.1.4. It is fixed in 2.4.6, 3.1.7, and 4.1.4, where recomposeAuthority rejects any port that is not a digit sequence per RFC 3986.",
"id": "UBUNTU-CVE-2026-84292",
"modified": "2026-09-04T00:00:00Z",
"published": "2026-09-04T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-84292"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84292"
},
{
"type": "REPORT",
"url": "https://github.com/fastify/fast-uri/security/advisories/GHSA-qw65-cvwx-89v3"
},
{
"type": "REPORT",
"url": "https://cna.openjsf.org/security-advisories.html"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-84292"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.