{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:7b38249a-eb0e-5183-9726-adf46e69bd5f", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6", "version": "12.2.17-tuxcare.6", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:09b82557-1814-579c-a160-3708ffa60e05", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66035 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.8." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:d9cc777f-b793-5747-b22b-2e320e9f76cc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 12.2.17-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:1be26940-be02-588d-80f8-3085139ca660", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 12.2.17-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:e612f0c3-434e-51f8-8554-715da72f1962", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 12.2.17-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:6632da1d-ced2-5c14-adcf-5b252fe8ab36", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 12.2.17-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:a9c26e07-0568-5b19-9bbd-06941d545c1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50168 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:a7be2963-feb6-5eb3-91e1-90c8fa0a99ea", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50169 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:6d0f497c-4f26-55b3-adb7-acb140932652", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50170 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:10376a0d-86b9-59f3-9eea-cdda031147a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50171 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:eb3073a1-b3f3-591b-9dd7-1b658b751cc8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50184 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:e0cb2f4c-ce62-520f-aa29-b6c21f8eec7a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50555 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:ed1404fe-6cec-53be-8419-ec1be476754f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50556 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:16e1eff5-3ff3-58b2-99fe-34877361615c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50557 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:e5a2eaa1-4d49-5e99-a27f-3681d473324d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-52725 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:4e296df1-179f-5cc7-96e7-c9bb17dd3c78", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54264 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:ae1b2043-bdb7-516b-801f-380f986de7ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54265 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:cb770bf8-8e9c-5d2a-a6fb-d873d9580503", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54266 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:475cc65f-f040-5def-8e8c-7c9337822be5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54267 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:e83cf3ae-70da-5a31-9619-69bedf7a64bf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54268 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.7." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:10b13c33-dce1-5249-af1a-251102463b68", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 12.2.17-tuxcare.6 of @angular/bazel. not_affected \u2014 Angular 12.2.17 does not contain the HttpTransferCache feature affected by CVE-2026-68945. HttpTransferCache, which caches HTTP requests during Server-Side Rendering (SSR), was first introduced in Angular 16.0.0\u2014approximately 4 major versions after the target version. The vulnerability concerns cache-key collision when repeated HTTP parameters are serialized, but since the entire HttpTransferCa...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:9d18772e-57e1-5d8e-9662-342fb0c14d9b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.9." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:628d0a59-1954-5626-9f03-b1d946f17c35", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 12.2.17-tuxcare.6 of @angular/bazel, and is fixed in 12.2.17-tuxcare.9." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:6170d867-2c09-5be0-a3e7-70049dbeeb90", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88056 affects version 12.2.17-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:c464824e-cadd-5030-9c0b-a6b823afb0e0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 12.2.17-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:aac93633-7860-5b2a-a2a8-31589c0b2e8f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 12.2.17-tuxcare.6 of @angular/bazel. not_affected \u2014 Angular 12.2.17-tuxcare.9 is not affected by CVE-2026-88059. The vulnerability requires HttpTransferCache, withRequestsMadeViaParent(), and provideClientHydration() features which were introduced in Angular 16.0.0. This version uses the older module-based HttpClientModule system and lacks the entire SSR hydration transfer-cache infrastructure. The vulnerable code pattern described in the CVE do...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ], "bom-ref": "urn:uuid:5df48442-01cc-5733-9511-969e037be682", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 12.2.17-tuxcare.6 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.6" } ] }