{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:df0824cf-32ef-5b4e-bc09-c1ae89afd134", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4", "type": "library", "name": "@angular/router", "version": "5.1.2-tuxcare.4", "purl": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:5d953fcc-3437-5f62-aea2-3a2f22ae1526", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bcf6d14e-498b-5472-8906-bfff806fc4f7", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2080a613-1b89-5e07-a9be-33b77df9570a", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:061dc2b0-5e95-564a-9adf-16995d4b5016", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5469d192-2e3a-5f51-b80b-929ea281188f", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:840ab9ed-1062-5ca5-9b8a-8eee5ca357a6", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 5.1.2-tuxcare.4 of @angular/router. not_affected \u2014 Angular version 5.1.2 is not affected by CVE-2026-41423. The vulnerability requires the WHATWG URL API which exhibits hostname override behavior with protocol-relative URLs. The target uses Node.js's legacy url.parse() API which does not have this behavior." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3376035a-7ff8-5d16-a40e-3302c74cf400", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:17badda9-a6a3-5daf-a7ae-a2c945a31421", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c6f7af31-8e13-5a50-9d24-ddf215a6d098", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0f0f8bb9-355d-58dc-8924-fb215fbb0ee6", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 5.1.2-tuxcare.4 of @angular/router. not_affected \u2014 no evidence captured" }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9be3f55a-a506-5744-98f9-efce67fa729b", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8112f37d-ea3d-50bf-9520-c38ad7696399", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9350c19d-5b82-5dc7-8497-0e2b69b07ca7", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f9c9fb34-7516-5d5b-b6bd-c6d454eee46b", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:73e3eb11-9b59-5d37-8aae-aaeba503fce1", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c5850bc1-dcf5-5f34-aca9-771339443b9d", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3777a046-7eba-5e52-ae4a-d37fa2a801b5", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 5.1.2-tuxcare.4 of @angular/router. not_affected \u2014 Angular v5.1.2-tuxcare.1 is NOT affected by CVE-2026-54264. The vulnerability requires a `newRequestWithMetadata` function that copies request headers, which does not exist in this version. The service worker reconstructs asset requests from URLs only using bare `adapter.newRequest(url)` calls, never copying or forwarding request headers. Therefore, credential headers cannot be leaked on cross-..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0c79870c-ad03-5e70-af0f-33657ef0aff1", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 5.1.2-tuxcare.4 of @angular/router. not_affected \u2014 Angular 5.1.2 uses the View Engine compiler architecture, which does not have the TwoWayProperty operation kind that is vulnerable in the Ivy compiler. In View Engine, two-way bindings desugar through the same parsePropertyBinding() code path as one-way bindings, ensuring both receive identical security context resolution and sanitization. The vulnerability pattern described in CVE-2026-54265 c..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2d76ffb9-035e-5be3-836d-92376458ab4e", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 5.1.2-tuxcare.4 of @angular/router. not_affected \u2014 Angular 5.1.2 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature that generates cache keys using a weak 32-bit DJB2 hash does not exist in this version. This feature was introduced in Angular v16+, while the target is v5.1.2. Although TransferState exists in this version for basic state transfer, there is no integration with HttpClient for automatic response caching, no..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e468a18e-89ad-5872-9a0b-19da45a3280e", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:80f58873-ac9f-5a92-a2a2-1b7953888abc", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8945e507-3859-50c8-b4bf-410265f74223", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.1.2-tuxcare.4 of @angular/router. not_affected \u2014 Angular 5.1.2 is not affected by CVE-2026-68945. The vulnerable component HttpTransferCache does not exist in this version. HttpTransferCache was introduced in Angular v16 (circa 2022), while this target is Angular 5.1.2 (2017-2018 era). Although Angular 5.1.2 has TransferState for basic SSR state transfer and HttpClient with HttpParams, it lacks the HTTP response caching mechanism during SSR t..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:442e79e1-3138-590d-8ea8-c9d97cbbc428", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cb8c7c51-8774-5f14-b003-dbc8c49122e5", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.1.2-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/router@5.1.2-tuxcare.4" } ] }