{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c985095f-612c-5cf2-908f-2b7c91865229", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9", "version": "5.2.11-tuxcare.9", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:ab964f49-a178-5ebf-9bdd-f86322bc1473", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:8b3301de-d04c-52b3-91e7-16419fed559f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:1712b2ee-6e81-5901-bf89-12dd8ef10951", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:e8312a3a-a2ec-5185-aaf3-9ae44be3c85f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:df4ce2df-231e-5b43-b23d-6f3ab4945b6c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:ecbf82fe-01d0-5f9c-949b-92f2dc11dd22", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:9a53184b-2478-5a73-b5cc-d470c8a90dc0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:e757e358-59fe-594c-80ba-ce4397281575", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:bc370b3d-bf09-5ca4-9f5e-dc20312a1d52", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:39f6631c-bd29-53f1-bfb4-616182a91b11", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:9cefd813-b94b-5242-9b0c-8fa7352487cf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:8bfb7080-1954-5a77-9413-001bc901d35b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:e1260a1b-5a14-58c7-820a-638869975a68", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:de08c533-56e6-5425-a8e7-ebf6bba7e115", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:684d769b-2ab4-5a3a-9539-bbb0702539cc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:702a4e9c-daf9-5f06-a725-7325e8ba438c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:4e8d980f-d4eb-5582-83ec-b570d28acb1a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:4f3f5185-4a95-56c6-bb7e-17a3c50b3814", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:4c5f0aeb-b4d7-5c5e-8176-e0f5e54cef22", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:68b1eae1-2f0e-5768-90a7-ef08b46eecf2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:3a752bc1-f6bb-5c85-a4f6-5bed393255da", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:044830e3-6bfe-56a4-ad2f-e12073c56605", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 5.2.11-tuxcare.9 of @angular/bazel, and is fixed in 5.2.11-tuxcare.13." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:d0e73242-36d7-5616-a8bb-712f67444fb1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 5.2.11-tuxcare.9 of @angular/bazel, and is fixed in 5.2.11-tuxcare.13." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:af0daceb-b5f4-55f5-a645-64bf0de7b316", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:29f7e1af-292a-59db-bd29-df8b37291ee6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.9 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ], "bom-ref": "urn:uuid:2dee53ff-9416-5935-8a18-fd35984dcdff", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:d9c2b48f-6851-5835-afad-bb17f88dbd1c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.9 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.9" } ] }