{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:b4a87d54-8456-5e5f-9e40-85a8cd021554", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23", "version": "5.2.11-tuxcare.23", "pedigree": { "ancestors": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@5.2.11", "type": "library", "version": "5.2.11" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:333cbb98-884c-55c4-b6b4-48c651e44cf0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:a639c150-46df-56de-b8b7-bd6e3aca7374", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:f74be16a-da2f-5d18-a882-70b7eb19b4d1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:5d5ad57b-5f50-5600-b537-d7f01c3b3e9b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:b4e066cc-dd62-5509-81cc-0b773b4fe72d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:b5c5fa98-3480-5009-a44b-4842797f8907", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:71f75631-e56a-5d0b-9de0-31c19adbdf22", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:b9a1fc78-461e-56d2-b77d-9f201f006ad2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:232eb606-71c4-562f-950f-a88bec0ad270", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:339fdf93-f712-5bca-a161-b5aad7da2631", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:dc484f5f-c91c-5f60-b951-1f2ee50be22a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:5587fb53-9424-58a6-a844-13cc5309da63", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:ef3003b2-82df-5335-8460-f42657b47976", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:69b9a793-92de-5e99-a316-9ffc33cd6093", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:14ddcc37-f0f2-5571-b9f9-e958e9e3593a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:85b2257e-fad6-5a33-89dc-280a079f6eb3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:d7814e75-47df-57c6-b698-73d1366e2cf9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:4eb1aace-a58e-517c-b577-9eda991fab71", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:21f53601-f06f-5c64-88f6-ff1829bf9080", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:02aaa057-6bbe-58ca-acd7-3590dad289a3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:243e6809-d643-5391-acd3-e55c3f89492f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:04c6f3a0-c180-51de-acaa-b44620025bf7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:c7720d8c-a52c-5a3e-bfec-77ac67eee19f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:141f263e-6b37-5826-98f8-1c621eeb95ec", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.23 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:526788c4-6980-5721-a2c3-203c21f1a5e5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:113b13e0-65ea-5c18-8a24-63e0ce800661", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:f353ce76-7a08-5bdc-b41c-116f86df04f4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.23 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...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:2988f2e6-a660-5316-8d7b-7c53ad7a9bea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:237430ca-ec05-5988-b640-bc7bb451ae83", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88058 does not affect version 5.2.11-tuxcare.23 of @angular/bazel. not_affected \u2014 CVE-2026-88058 affects the domino library's HTML serialization (XSS via ancestor fallback raw-content tag injection in comments/processing instructions during SSR). The target Angular 5.2.11-tuxcare.19 repository declares domino 2.1.2 as a dependency but does NOT vendor its source code. The vulnerable code (NodeUtils.js serializeOne() function) lives in the domino npm package, not in Angular's ...", "justification": "requires_dependency" } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:a4ae5356-0eba-5485-afc5-d64b508efcb2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.23 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ], "bom-ref": "urn:uuid:7e25077a-90ce-5fab-895b-667c95abbbe5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 5.2.11-tuxcare.23 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.23" } ] }