angular.js — security advisory
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.32, 21.2.24, and 22.2.0, the @angular/router URL parser stores numeric matrix parameter names and numeric outlet names as properties on initially empty JavaScript objects during Node.js server-side rendering. V8 can interpret these URL-derived keys as array indices and allocate dense backing stores sized to high numeric values, so repeated small path segments cause disproportionate per-segment heap consumption. An unauthenticated attacker can send overlapping requests containing repeated numeric matrix parameters when SSR is enabled, the router directly parses the request URL, and upstream proxies allow semicolons and multiple path segments, eventually exhausting the Node.js old-space heap and terminating the SSR worker. Pure client-side Angular applications are not affected. This issue is fixed in versions 20.3.32, 21.2.24, and 22.2.0.
- Products
- angular.js
- Affected versions
- 1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3
- Fixed versions
- Not specified
- CVEs
- CVE-2026-101896
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 23:35 UTC · Revision 1
Source evidence
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.32, 21.2.24, and 22.2.0, the @angular/router URL parser stores numeric matrix parameter names and numeric outlet names as properties on initially empty JavaScript objects during Node.js server-side rendering. V8 can interpret these URL-derived keys as array indices and allocate dense backing stores sized to high numeric values, so repeated small path segments cause disproportionate per-segment heap consumption. An unauthenticated attacker can send overlapping requests containing repeated numeric matrix parameters when SSR is enabled, the router directly parses the request URL, and upstream proxies allow semicolons and multiple path segments, eventually exhausting the Node.js old-space heap and terminating the SSR worker. Pure client-side Angular applications are not affected. This issue is fixed in versions 20.3.32, 21.2.24, and 22.2.0.
osv:DEBIAN-CVE-2026-101896
angular.js
Fixed versions: Not specified
angular.js
Fixed versions: Not specified
Complete source record
{
"id": "0e5685398eeda3cec29292e5c92cd7c78086fcb96b23581b921f8f54a3eca980",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-101896",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-101896",
"summary": "Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.32, 21.2.24, and 22.2.0, the @angular/router URL parser stores numeric matrix parameter names and numeric outlet names as properties on initially empty JavaScript objects during Node.js server-side rendering. V8 can interpret these URL-derived keys as array indices and allocate dense backing stores sized to high numeric values, so repeated small path segments cause disproportionate per-segment heap consumption. An unauthenticated attacker can send overlapping requests containing repeated numeric matrix parameters when SSR is enabled, the router directly parses the request URL, and upstream proxies allow semicolons and multiple path segments, eventually exhausting the Node.js old-space heap and terminating the SSR worker. Pure client-side Angular applications are not affected. This issue is fixed in versions 20.3.32, 21.2.24, and 22.2.0.",
"evidence": "osv:DEBIAN-CVE-2026-101896",
"products": [
{
"name": {
"value": "angular.js",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "1.8.3-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.8.3-1+deb12u1",
"evidence": "/affected/0/versions"
},
{
"value": "1.8.3-1+deb12u1~deb11u1",
"evidence": "/affected/0/versions"
},
{
"value": "1.8.3-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.8.3-3",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "angular.js",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "1.8.3-3",
"evidence": "/affected/1/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2026-101896",
"aliases": [
"DEBIAN-CVE-2026-101896"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "angular.js",
"purl": "pkg:deb/debian/angular.js?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"1.8.3-1",
"1.8.3-1+deb12u1",
"1.8.3-1+deb12u1~deb11u1",
"1.8.3-2",
"1.8.3-3"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-101896.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "angular.js",
"purl": "pkg:deb/debian/angular.js?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"1.8.3-3"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-101896.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-23T17:47:47.661191945Z",
"provider": "osv",
"upstream": [
"CVE-2026-101896"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-101896"
]
},
"related_cves": [
{
"value": "CVE-2026-101896",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 418975,
"published_at": "2026-10-14T16:17:29.013+00:00"
}