{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c62fd47c-7f2a-551e-a1c7-e534539fae1c", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14", "type": "library", "name": "@angular/bazel", "version": "5.2.11-tuxcare.14", "purl": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:25bf1cc8-f71e-5a24-a550-45064e1e5d99", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:7f827637-48a7-5b84-98dc-783ad8caca98", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:eb531546-7af8-53c3-a170-494a394c438e", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:f43e05ec-fd90-54cc-9936-7d1fcfbce973", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a51b787a-f615-5396-8aee-ae17a1ce1af4", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:77dc3788-f789-54e0-bb41-a5ee702a4496", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:4097d4f0-840b-50df-adc0-50ede1bda08a", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:098208f4-568e-579f-826f-6ae547efa2d4", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:10f10a80-7612-5b3c-bc49-4e5a13f63ebe", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:26e4a217-63a6-54a2-86e9-d7c7a9871046", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:cc861fd1-b69d-5486-b286-39f6e606ecce", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:4615a81f-fbac-5485-8475-d8a6a74377d7", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a707c251-c9b0-5534-a818-b1cb68b5cf3c", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a0d53d68-f91b-51c8-b767-1f959af07acd", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a5227a9e-0046-5790-91fb-a3454ff4ae0d", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a26a4d93-bfdf-5988-9ff5-5349406b1342", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:7dfc72d1-1625-5cc3-ab90-8b115344fbd1", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:0eb59325-fd4c-59ca-85b7-b2e1cf89c6e5", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:74d4d36c-3862-5cb1-82f1-9cfe0393d658", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:70677b86-e073-50ee-b043-31c3d1fd6882", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:5c1074c5-4007-581b-a59b-05c20d4b46c2", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:7de347cc-9793-58d8-8fa4-dd50c2737d75", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.14 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.14" } ] }, { "bom-ref": "urn:uuid:859b3d7d-486d-5828-987e-d8f76e58692a", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:0243d82b-ce9f-5fff-bf26-bfbafe31c847", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:346190df-509f-5b8b-8cfe-20b81894e1ab", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.14 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.14" } ] }, { "bom-ref": "urn:uuid:5305a6f6-d146-55ef-9e07-d39249345a2f", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:d689a3a9-a828-5259-9af7-f2126bc816d0", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.14 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.14" } ] }, { "bom-ref": "urn:uuid:d9ca6f0f-6519-51e3-bc2b-9102807819f4", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.14 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.14" } ] }