CVE-2026-110095
fast-uri vulnerable to improper path equivalence in relative reference normalization
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
3.7
fast-uri vulnerable to improper path equivalence in relative reference normalization
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
- Record
CVE-2026-110095- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-41
- Updated
- 2026-11-02
EUVDEUVD-2026-104812
3.7
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
- Record
EUVD-2026-104812- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-xhq7-xmqj-769h
3.7
fast-uri vulnerable to improper path equivalence in relative reference normalization
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.
- Record
GHSA-xhq7-xmqj-769h- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-41
- Updated
- 2026-11-02
NVD
3.7
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
- Record
CVE-2026-110095- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-41
- Updated
- 2026-11-02
OSV
3.7
fast-uri vulnerable to improper path equivalence in relative reference normalization
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
- Record
CVE-2026-110095- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-41
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-110095
3.7
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
- Record
DEBIAN-CVE-2026-110095- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
Show 19 moreShow less
OSVGHSA-xhq7-xmqj-769h
3.7
fast-uri vulnerable to improper path equivalence in relative reference normalization
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.
- Record
GHSA-xhq7-xmqj-769h- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-41
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-110095
3.7
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, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. 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, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.
- Record
UBUNTU-CVE-2026-110095- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSVCLSA-2026-1792486604 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 3.1.8-tuxcare.1.
- Record
CLSA-2026-1792486604- Updated
- 2026-11-02
OSVCLSA-2026-1792495022 No score
TuxCare security update for fast-uri (2 CVEs)
TuxCare rebuilt fast-uri to address 2 CVEs. Fixed in 3.1.7-tuxcare.2.
- Record
CLSA-2026-1792495022- Updated
- 2026-11-02
OSVCLSA-2026-1792505854 No score
TuxCare security update for fast-uri (2 CVEs)
TuxCare rebuilt fast-uri to address 2 CVEs. Fixed in 3.1.6-tuxcare.3.
- Record
CLSA-2026-1792505854- Updated
- 2026-11-02
OSVCLSA-2026-1792509177 No score
TuxCare security update for fast-uri (2 CVEs)
TuxCare rebuilt fast-uri to address 2 CVEs. Fixed in 3.1.5-tuxcare.5.
- Record
CLSA-2026-1792509177- Updated
- 2026-11-02
OSVCLSA-2026-1793097189 No score
TuxCare security update for fast-uri (1 CVE)
TuxCare rebuilt fast-uri to address 1 CVE. Fixed in 3.1.2-tuxcare.7.
- Record
CLSA-2026-1793097189- Updated
- 2026-11-02
OSVCLSA-2026-1793099940 No score
TuxCare security update for fast-uri (2 CVEs)
TuxCare rebuilt fast-uri to address 2 CVEs. Fixed in 3.0.1-tuxcare.7.
- Record
CLSA-2026-1793099940- Updated
- 2026-11-02
OSVCLSA-2026-1793099989 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 3.1.3-tuxcare.8.
- Record
CLSA-2026-1793099989- Updated
- 2026-11-02
OSVCLSA-2026-1793100398 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 3.1.0-tuxcare.5.
- Record
CLSA-2026-1793100398- Updated
- 2026-11-02
OSVCLSA-2026-1793100671 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 3.1.4-tuxcare.6.
- Record
CLSA-2026-1793100671- Updated
- 2026-11-02
OSVCLSA-2026-1793101572 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 2.4.0-tuxcare.5.
- Record
CLSA-2026-1793101572- Updated
- 2026-11-02
OSVCLSA-2026-1793101610 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 2.4.7-tuxcare.2.
- Record
CLSA-2026-1793101610- Updated
- 2026-11-02
OSVCLSA-2026-1793101657 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 2.4.5-tuxcare.5.
- Record
CLSA-2026-1793101657- Updated
- 2026-11-02
OSVCLSA-2026-1793101678 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 3.0.6-tuxcare.5.
- Record
CLSA-2026-1793101678- Updated
- 2026-11-02
OSVCLSA-2026-1793111428 No score
TuxCare security update for fast-uri (3 CVEs)
TuxCare rebuilt fast-uri to address 3 CVEs. Fixed in 2.4.3-tuxcare.6.
- Record
CLSA-2026-1793111428- Updated
- 2026-11-02
OSVCLSA-2026-1793125156 No score
TuxCare security update for fast-uri (4 CVEs)
TuxCare rebuilt fast-uri to address 4 CVEs. Fixed in 2.4.2-tuxcare.5.
- Record
CLSA-2026-1793125156- Updated
- 2026-11-02
OSVCLSA-2026-1793125297 No score
TuxCare security update for fast-uri (2 CVEs)
TuxCare rebuilt fast-uri to address 2 CVEs. Fixed in 3.0.3-tuxcare.7.
- Record
CLSA-2026-1793125297- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:12261-1 No score
git-bug-0.11.0-3.1 on GA media
These are all security issues fixed in the git-bug-0.11.0-3.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:12261-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
fast-urinpm |
before 2.4.8 | 2.4.8 |
fast-urinpm |
3.0.0 up to 3.1.9 | 3.1.9 |
fast-urinpm |
4.0.0 up to 4.2.3 | 4.2.3 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
3.1.8-tuxcare.0 up to 3.1.8-tuxcare.1, plus listed versions 3.1.8 |
3.1.8-tuxcare.1 |
fast-uriTuxCare:npm From an advisory covering 2 CVEs |
3.1.7-tuxcare.0 up to 3.1.7-tuxcare.2, plus listed versions 3.1.73.1.7-tuxcare.1 |
3.1.7-tuxcare.2 |
fast-uriTuxCare:npm From an advisory covering 2 CVEs |
3.1.6-tuxcare.0 up to 3.1.6-tuxcare.3, plus listed versions 3.1.63.1.6-tuxcare.13.1.6-tuxcare.2 |
3.1.6-tuxcare.3 |
fast-uriTuxCare:npm From an advisory covering 2 CVEs |
3.1.5-tuxcare.0 up to 3.1.5-tuxcare.5, plus listed versions 3.1.53.1.5-tuxcare.13.1.5-tuxcare.23.1.5-tuxcare.33.1.5-tuxcare.4 |
3.1.5-tuxcare.5 |
fast-uriTuxCare:npm |
3.1.2-tuxcare.0 up to 3.1.2-tuxcare.7, plus listed versions 3.1.23.1.2-tuxcare.13.1.2-tuxcare.23.1.2-tuxcare.33.1.2-tuxcare.43.1.2-tuxcare.53.1.2-tuxcare.6 |
3.1.2-tuxcare.7 |
fast-uriTuxCare:npm From an advisory covering 2 CVEs |
3.0.1-tuxcare.0 up to 3.0.1-tuxcare.7, plus listed versions 3.0.13.0.1-tuxcare.13.0.1-tuxcare.23.0.1-tuxcare.33.0.1-tuxcare.43.0.1-tuxcare.53.0.1-tuxcare.6 |
3.0.1-tuxcare.7 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
3.1.3-tuxcare.0 up to 3.1.3-tuxcare.8, plus listed versions 3.1.33.1.3-tuxcare.13.1.3-tuxcare.23.1.3-tuxcare.33.1.3-tuxcare.43.1.3-tuxcare.53.1.3-tuxcare.63.1.3-tuxcare.7 |
3.1.3-tuxcare.8 |
Show 19 moreShow less
| Package | Affected | Fixed |
|---|---|---|
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
3.1.0-tuxcare.0 up to 3.1.0-tuxcare.5, plus listed versions 3.1.03.1.0-tuxcare.13.1.0-tuxcare.23.1.0-tuxcare.33.1.0-tuxcare.4 |
3.1.0-tuxcare.5 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
3.1.4-tuxcare.0 up to 3.1.4-tuxcare.6, plus listed versions 3.1.43.1.4-tuxcare.13.1.4-tuxcare.23.1.4-tuxcare.33.1.4-tuxcare.43.1.4-tuxcare.5 |
3.1.4-tuxcare.6 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
2.4.0-tuxcare.0 up to 2.4.0-tuxcare.5, plus listed versions 2.4.02.4.0-tuxcare.12.4.0-tuxcare.22.4.0-tuxcare.32.4.0-tuxcare.4 |
2.4.0-tuxcare.5 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
2.4.7-tuxcare.0 up to 2.4.7-tuxcare.2, plus listed versions 2.4.72.4.7-tuxcare.1 |
2.4.7-tuxcare.2 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
2.4.5-tuxcare.0 up to 2.4.5-tuxcare.5, plus listed versions 2.4.52.4.5-tuxcare.12.4.5-tuxcare.22.4.5-tuxcare.32.4.5-tuxcare.4 |
2.4.5-tuxcare.5 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
3.0.6-tuxcare.0 up to 3.0.6-tuxcare.5, plus listed versions 3.0.63.0.6-tuxcare.13.0.6-tuxcare.23.0.6-tuxcare.33.0.6-tuxcare.4 |
3.0.6-tuxcare.5 |
fast-uriTuxCare:npm From an advisory covering 3 CVEs |
2.4.3-tuxcare.0 up to 2.4.3-tuxcare.6, plus listed versions 2.4.32.4.3-tuxcare.12.4.3-tuxcare.22.4.3-tuxcare.32.4.3-tuxcare.42.4.3-tuxcare.5 |
2.4.3-tuxcare.6 |
fast-uriTuxCare:npm From an advisory covering 4 CVEs |
2.4.2-tuxcare.0 up to 2.4.2-tuxcare.5, plus listed versions 2.4.22.4.2-tuxcare.12.4.2-tuxcare.22.4.2-tuxcare.32.4.2-tuxcare.4 |
2.4.2-tuxcare.5 |
fast-uriTuxCare:npm From an advisory covering 2 CVEs |
3.0.3-tuxcare.0 up to 3.0.3-tuxcare.7, plus listed versions 3.0.33.0.3-tuxcare.13.0.3-tuxcare.23.0.3-tuxcare.33.0.3-tuxcare.43.0.3-tuxcare.53.0.3-tuxcare.6 |
3.0.3-tuxcare.7 |
node-ajvDebian:12 |
All versions, plus listed versions 6.12.6-38.11.2~ds+~2.1.1-18.12.0~ds+~2.1.1-18.12.0~ds+~2.1.1-28.12.0~ds+~2.1.1-3 Show 19 moreShow less8.12.0~ds+~2.1.1-48.12.0~ds+~2.1.1-58.17.1~ds+~3.0.1+~3.1.0-18.17.1~ds+~3.0.1+~3.1.0-28.17.1~ds+~3.0.1+~3.1.0-38.17.1~ds+~3.0.1+~3.1.0-48.18.0~ds+~cs6.1.1-18.18.0~ds+~cs6.1.1-28.20.0~ds+~cs6.1.3-18.20.0~ds+~cs7.1.2-18.20.0~ds+~cs7.1.3-18.20.0~ds+~cs7.1.3-28.20.0~ds+~cs7.1.3-38.20.0~ds+~cs7.1.4-18.20.0~ds+~cs7.1.5-18.20.0~ds+~cs7.1.6-18.20.0~ds+~cs7.1.6-28.20.0~ds+~cs7.2.4-18.8.2~ds+~2.1.1-1 |
None known |
node-ajvDebian:13 |
All versions, plus listed versions 8.12.0~ds+~2.1.1-58.17.1~ds+~3.0.1+~3.1.0-18.17.1~ds+~3.0.1+~3.1.0-28.17.1~ds+~3.0.1+~3.1.0-38.17.1~ds+~3.0.1+~3.1.0-4 Show 12 moreShow less8.18.0~ds+~cs6.1.1-18.18.0~ds+~cs6.1.1-28.20.0~ds+~cs6.1.3-18.20.0~ds+~cs7.1.2-18.20.0~ds+~cs7.1.3-18.20.0~ds+~cs7.1.3-28.20.0~ds+~cs7.1.3-38.20.0~ds+~cs7.1.4-18.20.0~ds+~cs7.1.5-18.20.0~ds+~cs7.1.6-18.20.0~ds+~cs7.1.6-28.20.0~ds+~cs7.2.4-1 |
None known |
node-ajvDebian:14 |
before 8.20.0~ds+~cs7.2.4-1, plus listed versions 8.12.0~ds+~2.1.1-58.17.1~ds+~3.0.1+~3.1.0-18.17.1~ds+~3.0.1+~3.1.0-28.17.1~ds+~3.0.1+~3.1.0-38.17.1~ds+~3.0.1+~3.1.0-4 Show 11 moreShow less8.18.0~ds+~cs6.1.1-18.18.0~ds+~cs6.1.1-28.20.0~ds+~cs6.1.3-18.20.0~ds+~cs7.1.2-18.20.0~ds+~cs7.1.3-18.20.0~ds+~cs7.1.3-28.20.0~ds+~cs7.1.3-38.20.0~ds+~cs7.1.4-18.20.0~ds+~cs7.1.5-18.20.0~ds+~cs7.1.6-18.20.0~ds+~cs7.1.6-2 |
8.20.0~ds+~cs7.2.4-1 |
node-ajvUbuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1 |
None known |
node-ajvUbuntu:20.04:LTS |
All versions, plus listed versions 6.10.2-1 |
None known |
node-ajvUbuntu:22.04:LTS |
All versions, plus listed versions 6.12.6-26.12.6-3 |
None known |
node-ajvUbuntu:24.04:LTS |
All versions, plus listed versions 6.12.6-38.12.0~ds+~2.1.1-4 |
None known |
node-ajvUbuntu:26.10 |
All versions, plus listed versions 8.17.1~ds+~3.0.1+~3.1.0-4build18.20.0~ds+~cs6.1.3-18.20.0~ds+~cs7.1.2-18.20.0~ds+~cs7.1.3-18.20.0~ds+~cs7.1.3-3 |
None known |
node-ajvUbuntu:26.04:LTS |
All versions, plus listed versions 8.12.0~ds+~2.1.1-58.17.1~ds+~3.0.1+~3.1.0-28.17.1~ds+~3.0.1+~3.1.0-4build1 |
None known |
git-bugopenSUSE:Tumbleweed From an advisory covering 13 CVEs |
before 0.11.0-3.1 | 0.11.0-3.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| affected, aliases, references | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-110095 is a low vulnerability (CVSS 3.7) in Fast-uri, published October 20, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.29%, the 21st percentile. Fixed in fast-uri 2.4.8.
References
github.com/fastify/fast-uri/security/advisories/GHSA-xhq7-xmqj-769h
cna.openjsf.org/security-advisories.html
nvd.nist.gov/vuln/detail/CVE-2026-110095
github.com/fastify/fast-uri/commit/048bbd0a252971be86d6579f0dfc87f8de5b9c47
github.com/fastify/fast-uri/commit/52774a5c35df36b0bbe439cd4c12c3dc0e50e3b9
github.com/fastify/fast-uri/commit/7c19f8b97ec51f1f20b4e3d9d5820cb8d5176058
Show 25 moreShow less
github.com/fastify/fast-uri/commit/9eb8759a9825c046f57f7f695f1944bc39b88abd
github.com/fastify/fast-uri/commit/acc5c5d60c4209571789496e1732468911c7e12a
github.com/fastify/fast-uri/commit/b110a3571c37dfcf9d1c72ce2e2e178c78d1a424
github.com/fastify/fast-uri/releases/tag/v2.4.8
github.com/fastify/fast-uri/releases/tag/v3.1.9
github.com/fastify/fast-uri/releases/tag/v4.2.3
github.com/advisories/GHSA-xhq7-xmqj-769h
github.com/CVEProject/cvelistV5/tree/main/cves/2026/110xxx/CVE-2026-110095.json
security-tracker.debian.org/tracker/CVE-2026-110095
github.com/fastify/fast-uri
ubuntu.com/security/CVE-2026-110095
cve.org/CVERecord?id=CVE-2026-110095
suse.com/security/cve/CVE-2026-110095
suse.com/security/cve/CVE-2026-110180
suse.com/security/cve/CVE-2026-110306
suse.com/security/cve/CVE-2026-110725
suse.com/security/cve/CVE-2026-110816
suse.com/security/cve/CVE-2026-111756
suse.com/security/cve/CVE-2026-112085
suse.com/security/cve/CVE-2026-112366
suse.com/security/cve/CVE-2026-78659
suse.com/security/cve/CVE-2026-78660
suse.com/security/cve/CVE-2026-78663
suse.com/security/cve/CVE-2026-78669
suse.com/security/cve/CVE-2026-97032