{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:5baefe37-21f5-5083-b364-c85a74b14258", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4", "type": "library", "name": "@angular/router", "version": "11.2.0-tuxcare.4", "purl": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:a781a372-a77c-521a-8eb1-8618c24a5323", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9b08b4fd-317d-5733-a10c-cdfe315d576e", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4020982e-0545-5206-935c-92dfcabc35c2", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:05c5c053-0a9b-581f-a9a6-d1f08a2512ee", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:88a02277-2c15-5709-9669-a7d93d7ede2e", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.4 of @angular/router. not_affected \u2014 Target version 11.2.0 uses Node.js url.parse() API which does not perform hostname hijacking with protocol-relative URLs. The SSRF vulnerability (CVE-2026-41423) specifically affects versions using WHATWG URL constructor without the defense. The target's url.parse() produces empty hostname for inputs like '//evil.com', preventing the SSRF exploitation that requires hostname replacement." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8ad7ad97-39b2-541e-a8aa-88242acc13a9", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d38b7389-5b75-5f66-bd16-ec7a17156b1f", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bd66f4a2-42b0-5998-9a0c-413f4f4084ff", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8cb84d2e-37e3-52f5-a7e3-a25b5ffcdd81", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.4 of @angular/router. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-50170. The vulnerability exists in Angular's HTTP transfer cache feature, which automatically caches HTTP responses during server-side rendering (SSR) and reuses them during client hydration. This feature was introduced in Angular v16+ and does not exist in Angular 11.2.0. The target repository lacks the vulnerable code path entirely: no transfer_cache..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:18effeb4-228c-5322-9223-04330de55069", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d0a395b5-b438-538a-ba58-48e3deefa08f", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a77b0704-567b-523e-8654-6e59aa15066b", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c7b0704c-61f9-5073-b18e-176b9c4fdd0d", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:eb653555-3866-5058-bb55-3dedc67b7bfb", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f3a210e0-b2c6-5c30-9f8b-5b126cf34a0a", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bc20a4f8-3e70-5b11-b382-b1452c22bf27", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.4 of @angular/router. not_affected \u2014 Version 11.2.0-tuxcare.2 is NOT affected by CVE-2026-54264. This version lacks the vulnerable code pattern - asset-group requests are reconstructed using URL-only (no headers forwarded), and data-group requests use browser's native fetch which strips sensitive headers per Fetch specification. The vulnerability requires a header-copying mechanism that does not exist in this version." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a64fe540-56da-5643-bc28-e0e6ef5ad1a2", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.4 of @angular/router. not_affected \u2014 Angular v11.2.0-tuxcare.2 is NOT affected by CVE-2026-54265. The vulnerability requires the Ivy template compiler pipeline's TwoWayProperty IR operation introduced in later versions (v20+). This version uses an earlier compiler architecture (View Engine + early Ivy) where two-way property bindings are desugared through the same parsePropertyBinding() path as one-way bindings, applying schema-de..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dcd7eada-a010-5796-9f75-e86f91201469", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.4 of @angular/router. not_affected \u2014 Angular v11.2.0 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature (introduced in Angular v16+) does not exist in this version. The transfer_cache.ts file and all related APIs (HttpTransferCache, generateHash, makeCacheKey, withHttpTransferCache) are completely absent from the codebase." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e1c351fc-8b02-5cac-a364-7e150b6e0a1b", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c09cd293-2d97-5458-a144-07899c01da5f", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cada2604-83d7-5c08-a051-713723f89641", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.4 of @angular/router. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-68945. The vulnerability exists in HttpTransferCache, a feature for automatically caching HTTP requests during Server-Side Rendering (SSR). This feature does not exist in Angular 11.2.0. HttpTransferCache was introduced in Angular v16+ as part of the modernized SSR architecture. The target version predates this feature by multiple major releases. Only ..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:74bb7079-c8b2-5fb1-b757-5700c41602ec", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:37fdb1fa-88de-560e-aafb-56c084a53312", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/router@11.2.0-tuxcare.4" } ] }