{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:19eafb7a-d90a-5c64-b40e-28d749cf3715", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19", "type": "library", "name": "@angular/bazel", "version": "5.2.11-tuxcare.19", "purl": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:e140d8a8-36e4-5385-95ca-7d9aa39950e5", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:fcfe4dfd-88ca-5f19-a189-80f0efe175ae", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:b01f9043-e57d-5635-ba96-9e93683f7171", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:484ff26a-21c0-55c5-95d8-e0aeb1972186", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:e71da7c1-5dd2-5206-85fa-015aba00643f", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:2da9f0e2-55a5-5d0a-a3e6-ffdaa0a604ef", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:6b409d17-fd95-5502-96be-6996178fa5bd", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:de6036ec-840d-53de-909a-51fb1f437971", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:ee6a350b-6662-522b-a54a-951f3f9e855e", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:6f9fd63f-b815-5332-a7ea-2df548e431df", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:656f8a0f-77f9-55cd-8537-663d8b7b4bf0", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:7ec9b7b1-44c6-591b-8d98-a807cfa2df80", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:a2ad429c-252d-5219-b288-1c9074ef4919", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:5fff8a76-0ad7-5fbf-987d-722d2052d592", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:7969ba77-244e-5a62-b77a-f9dd4c601f02", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:21833e78-5ad1-57b6-9b24-9bf72afae7db", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:12069a9b-1df7-582b-8eb3-a1260b906b58", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:df214b48-0f55-525d-b619-7dbe92e5c430", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:6491a64e-e325-521a-80c7-b86b56c1283b", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:5e42c2e5-68d4-5703-b9c9-a0ec7f4ccd07", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:ee88781e-2d51-593d-89c7-e1bbc05be67e", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:a3d22980-6fe5-5090-9fac-4967fe3c3589", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.19 of @angular/bazel. not_affected \u2014 Angular 5.2.11 is NOT affected by CVE-2026-68945. The vulnerable component `HttpTransferCache` does not exist in this version. This feature was introduced in Angular v16 as part of the modern SSR hydration system. Angular 5.2.11 only has the basic `TransferState` API (a generic key-value store for manual state transfer), not the automatic HTTP request caching interceptor that contains the vulne..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:e1feec4e-eb3b-5629-8aa3-7ad478b26e4f", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:b883f55f-b226-58d5-9256-b474a7d2a0a5", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:2a406db5-ce48-5ee6-981e-03541b15e78a", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.19 of @angular/bazel. not_affected \u2014 Angular 5.2.11-tuxcare.19 does not contain the vulnerable URL resolution code pattern described in CVE-2026-88056. The vulnerability requires the url.ts file with parseUrl function calling String.prototype.trim() and the relativeUrlsTransformerInterceptorFn HTTP interceptor, both introduced in later Angular versions (post-June 2026). The target version uses a fundamentally different architectur..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:0c040fc9-759e-58fc-aa11-8a54c4da0d74", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:593d8c4b-9aa0-57dd-b1a2-f481c52ea8eb", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.19 of @angular/bazel. not_affected \u2014 Angular 5.2.11 is NOT AFFECTED by CVE-2026-88059. The vulnerability requires HttpTransferCache with hierarchical HttpClient delegation (withRequestsMadeViaParent()), features that were introduced in Angular v16. Angular 5.2.11 predates these features by approximately 6+ years and contains only a basic HTTP interceptor architecture with no automatic response caching mechanism. While TransferStat..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:b4e30573-8850-58a9-973c-b43f5172b532", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.19 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.19" } ] }