{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:35abf28d-9266-5ff0-9690-c539e586a102", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4", "type": "library", "name": "@angular/bazel", "version": "5.1.2-tuxcare.4", "purl": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:58d2f485-9098-5f55-833b-4c47950e0d5a", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7cce40fa-de27-515d-8e6f-2697b12610ba", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6c99a88d-3baa-51ac-9fe7-56dd5e0745d3", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:48aeca53-c29d-5902-87b8-615a526205b0", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:33bf9e63-47cd-52f9-8192-f4fbd345b83c", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6438ac08-02fe-599f-a8c9-f137e4e13c4e", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 5.1.2-tuxcare.4 of @angular/bazel. 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/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3229b186-e4be-5dfe-b580-1de049d65d00", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1f87c550-f451-5af3-93db-60cc4496aa3a", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fbf10710-c7c5-5a0b-89b8-d198a179d7f4", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:96cf2c75-dad9-5e03-a9dc-b32716e1325e", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 5.1.2-tuxcare.4 of @angular/bazel. not_affected \u2014 no evidence captured" }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fb2e2af5-4523-5df9-bfab-9597438df83c", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1c892cb6-77bb-535e-882b-16981097a2bb", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a1e7012f-dad6-5202-b772-ea8f442ca721", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a6a30bdb-b031-5c5d-b47b-17fd42c2812c", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7651fb7e-f9bf-5536-8a07-eb947cabc305", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:19860370-9ad0-5a4f-884f-e0b3bbc18e40", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:02529f9e-8adc-5828-8a7d-9d922d54cb94", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 5.1.2-tuxcare.4 of @angular/bazel. 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/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8dadb05c-db96-5cd2-ad36-6276e6218bfc", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 5.1.2-tuxcare.4 of @angular/bazel. 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/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:acfce4c6-4290-56c9-9045-fa9cf34aa870", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 5.1.2-tuxcare.4 of @angular/bazel. 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/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:77e5a852-5213-5577-9b1f-0582d5a0565d", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8090dccd-427a-5e94-835b-0458fe9e21fb", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:16464b81-e218-5613-a5f9-43a847c58b31", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.1.2-tuxcare.4 of @angular/bazel. 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/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c428177d-e7f0-594b-be67-664ef3b7e6ac", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1e4448c4-f170-5902-952c-1db9c1990bf1", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.1.2-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@5.1.2-tuxcare.4" } ] }