{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:2d6cd6a7-8c30-507f-9397-e9dfb35067af", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14", "version": "7.2.16-tuxcare.14", "pedigree": { "ancestors": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@7.2.16", "type": "library", "version": "7.2.16" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:7de8eabb-f7f9-5f33-b3a9-95783dd3e617", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:faaabdf4-e150-54df-83ca-f63b69b28e88", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:1e290937-e318-5f90-8edd-d607532a7e8a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:20120072-8f3e-56ca-8b05-978bd3ebb571", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:001a6d7a-1f3e-5a3a-848a-e883d5736b39", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:4d0ee869-d2de-5abf-8032-b7ebc190b212", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:531610d0-9664-5c1b-8b48-4f1fc4373a15", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:1c580b5c-5cac-514e-b2fc-fc26c1042dc8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:953669b9-058e-5e02-86dc-302b497d1c0d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:9e80185a-b512-5c78-bd63-678d8f1bf28c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:22182848-c332-5889-af9b-2a805aff5636", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:c2827f11-de4b-5bc5-a2ae-30d0a72117f1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:9d59d54f-5f40-5823-9796-9ae899728b4b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:7fa668ee-1171-5dea-9049-d25bdd476dad", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:f8f957dc-9c0e-5740-8300-ab58e588a91d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:aea0eb3b-daff-5f13-bc8f-876eb69760fb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:87f9a85c-589f-5c3d-acd3-7e3b0422e6e0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:408a1e7a-9c85-58c5-aabf-bf04fe3ac4b6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:99456037-e918-5459-a0a3-c47329ebeee8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:2668a4ba-d7df-51b1-8eed-a90997afe39c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:86b8c051-c0f6-581e-bed8-cd9abca8bcee", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:e126a127-1313-5e3b-a253-d1d661dda08d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:c3d669ed-425f-5aae-acb0-7e62d1cc59a9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:c2d0454c-a20e-599c-8389-058f84f7ee86", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.16-tuxcare.14 of @angular/bazel. not_affected \u2014 Angular 7.2.16 is not affected by CVE-2026-68945. The vulnerability concerns HttpTransferCache's cache key generation logic that treats repeated HTTP parameters (`?role=user&role=admin`) and comma-separated values (`?role=user,admin`) as identical, causing cache key collisions. However, the HttpTransferCache feature does not exist in version 7.2.16\u2014it was introduced in Angular v16. While v7.2.1...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:a9b174f0-a325-5183-8ff6-12e09a4a4e02", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:1f127890-332b-5cfc-9fc2-80df6cfeac7d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:f5f5dbac-4bdf-5f00-b814-9560009e4471", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.16-tuxcare.14 of @angular/bazel. not_affected \u2014 Angular 7.2.16 is not affected by CVE-2026-88056. The vulnerability requires a String.prototype.trim() call on URLs during server-side rendering that strips Unicode whitespace characters, converting same-origin relative URLs into cross-origin protocol-relative URLs. This vulnerable code pattern does not exist in Angular 7.2.16. The CVE describes a vulnerability introduced in later Angular versi...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:e4a704e1-3183-576d-a102-33a690d72abe", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88057 does not affect version 7.2.16-tuxcare.14 of @angular/bazel. not_affected \u2014 Angular 7.2.16 is not affected by CVE-2026-88057. The vulnerability exists in the Ivy compiler's template pipeline (introduced in Angular 9+), which does not exist in this version. Angular 7.2.16 uses View Engine, where the SecurityContext determination for directive host bindings correctly uses the concrete host element name (`element.name`) rather than the directive's selector. The exploitati...", "justification": "code_not_present" } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:717a87cc-f3e7-5066-8b0c-ec6267ecc494", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:3a67ea93-5228-5915-8544-e46f2dc4cd35", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.16-tuxcare.14 of @angular/bazel. not_affected \u2014 Angular 7.2.16 is not affected by CVE-2026-88059. The vulnerability requires HttpTransferCache, withRequestsMadeViaParent(), and client hydration features that were introduced in Angular v16+. Angular 7.2.16 predates these features by approximately 7 major versions. The codebase contains only legacy TransferState (manual key-value store) and NgModule-based HttpClient (no hierarchical delegation...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ], "bom-ref": "urn:uuid:46f56298-7d12-548a-8242-91a0f179926b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.16-tuxcare.14 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@7.2.16-tuxcare.14" } ] }