{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:7965c6c9-97f7-5871-a874-72533cd7a30d", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4", "version": "12.2.17-tuxcare.4", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:b7596bac-2234-5b40-bca9-0b48dd5a14fa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66035 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:0a0b9f98-8978-5e23-be5f-c9c3075b466b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 12.2.17-tuxcare.4 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:f642fc51-7eda-5a69-82cf-7df711acbbb2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 12.2.17-tuxcare.4 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:032f05ee-1492-5d3b-8d8e-b7bc66cd7b97", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 12.2.17-tuxcare.4 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:0539c8ae-4e16-5d70-b4ae-f21f8431ef1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46417 affects version 12.2.17-tuxcare.4 of @angular/bazel, and is fixed in 12.2.17-tuxcare.6." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:d4468d93-0ce9-5cf0-ad07-81ca4dd75591", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50168 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:b34f72c6-be1c-5e18-9a9d-532dc2653cc8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50169 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:30dbabaf-0ce1-5f86-8d43-f513be01123e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50170 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:4c605d19-d130-5dd4-b6ae-ab689eb1c193", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50171 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:aacec046-c25c-5be9-aaa9-793e8f0492fd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50184 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:0c29364d-1695-5ee2-9a00-1ed756746ab2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50555 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:289b6fde-920c-55d7-914a-25272be2d507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50556 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:53eecc5a-7d15-54f2-a1cc-03783afb1271", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50557 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:1f3ebdc3-9090-51d3-bece-2d54744bba29", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-52725 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:7c076c54-e2ab-579a-8cb7-d6aea82edb42", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54264 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:77e6cf6c-5d03-5fa0-8ab5-68822836348b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54265 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:ebcc9bbb-b0ce-5580-8956-bab5b2a6dfb1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54266 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:ab949387-e6ec-5ebc-8666-66ea6ce1b681", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54267 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:7e6090fc-10a0-53fc-ae9c-492a043e5e7d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54268 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:d1c1779b-6b20-58c1-b300-e5ddaa6ab141", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:3db69385-e37b-5a19-9b47-5e2a9c3a6325", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:d82dae9b-77e2-5e06-9fea-1fa7ec4993ba", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:0cee2ed0-f215-592a-88cf-24ef03e70b8e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88056 affects version 12.2.17-tuxcare.4 of @angular/bazel." } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:b05da2dd-5ab0-5971-a983-4e2ba5c92b64", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 12.2.17-tuxcare.4 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ], "bom-ref": "urn:uuid:4f058690-0fbb-5705-ae0f-220cfdad123b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 12.2.17-tuxcare.4 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.4" } ], "bom-ref": "urn:uuid:9ceed815-1fcd-5d0c-8dac-dad8e38793ea", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 12.2.17-tuxcare.4 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@12.2.17-tuxcare.4" } ] }