ubuntu-cve-2026-4867
Vulnerability from osv_ubuntu
Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. The backtrack protection added in path-to-regexp@0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, so capture groups overlap and cause catastrophic backtracking. Patches: Upgrade to path-to-regexp@0.1.13 Custom regex patterns in route definitions (e.g., /:a-:b([^-/]+)-:c([^-/]+)) are not affected because they override the default capture group. Workarounds: All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b-:c to /:a-:b([^-/]+)-:c([^-/]+). If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-path-to-regexp",
"binary_version": "1.0.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "node-path-to-regexp",
"purl": "pkg:deb/ubuntu/node-path-to-regexp@1.0.1-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-path-to-regexp",
"binary_version": "1.0.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "node-path-to-regexp",
"purl": "pkg:deb/ubuntu/node-path-to-regexp@1.0.1-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-path-to-regexp",
"binary_version": "6.1.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "node-path-to-regexp",
"purl": "pkg:deb/ubuntu/node-path-to-regexp@6.1.0-2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.0-2",
"3.1.0-1",
"6.1.0-2"
]
}
],
"aliases": [],
"details": "Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. The backtrack protection added in path-to-regexp@0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, so capture groups overlap and cause catastrophic backtracking. Patches: Upgrade to path-to-regexp@0.1.13 Custom regex patterns in route definitions (e.g., /:a-:b([^-/]+)-:c([^-/]+)) are not affected because they override the default capture group. Workarounds: All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b-:c to /:a-:b([^-/]+)-:c([^-/]+). If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length.",
"id": "UBUNTU-CVE-2026-4867",
"modified": "2026-04-02T17:29:41Z",
"published": "2026-03-26T17:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-4867"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4867"
},
{
"type": "REPORT",
"url": "https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-37ch-88jc-xwx2"
},
{
"type": "REPORT",
"url": "https://blakeembrey.com/posts/2024-09-web-redos"
},
{
"type": "REPORT",
"url": "https://cna.openjsf.org/security-advisories.html"
},
{
"type": "REPORT",
"url": "https://github.com/advisories/GHSA-9wv6-86v2-598j"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-4867"
],
"withdrawn": "2026-05-21T12:08:04Z"
}
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.