{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:9994078d-8968-5aad-a015-c35d4f149fb9", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/core", "purl": "pkg:npm/%40angular/core@7.2.16-tuxcare.12", "type": "library", "bom-ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12", "version": "7.2.16-tuxcare.12", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:ff08b54d-fc18-52bb-b214-7ecab031917a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:6c2816b6-1e39-56e9-9f10-416717b7d4ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:0f5cb783-67e3-5b3c-85d0-ba72425643d3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:abaee274-9986-5709-9a64-d486b4a411da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:a2cc9d7c-a684-5f96-8d02-2265638fa4cf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:8c59b68b-d4e3-5bf1-80d2-4f0718b76976", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:39397115-f357-56e2-88e7-42b18ead84a4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:6e3fc2d7-9864-590a-9704-ab8fc9e52f31", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:d66b47cd-1162-5fb3-bd6b-2301a34cc81f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:02952537-5c23-535e-9493-a286c3ab2134", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:d27ac6ec-d0e8-5157-a575-18f1e97e3ee5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:3029149d-2235-51f0-91c9-b4c489250e23", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:6f261233-f6bd-5825-9889-79c9932a04b1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:ff44f07e-52c8-5b87-8c70-761aa2e33862", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:f4702255-c79b-5e1a-9217-503ffb0b0a4d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:4e2b0e25-6c6f-5572-8f3b-f0138bc48f7e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:cd9c36a1-eaa1-5a38-a1ac-e3792c8269b6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:d8810d2f-f9ce-58d6-b08e-440db6c6cfff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:4c4a1242-80f1-55d0-b4a2-05b2689f529a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:62a77ab9-7d39-57dc-8d81-4ac4d91a1573", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:e36fd3db-ee9f-5749-bcc7-e81a643fc478", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:e8cf4056-d7fe-5c21-a04b-871af0434612", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.16-tuxcare.12 of @angular/core. 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/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:936a0641-00c5-5802-97f4-4893e598e8a7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:39a5010c-2f0b-5aee-a3bc-653bf9614553", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:62ced0b1-eda1-56ff-8709-00dccfe02899", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.16-tuxcare.12 of @angular/core. 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/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:a56c713b-42e4-5e9b-8695-eaa9ecc332d2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88057 does not affect version 7.2.16-tuxcare.12 of @angular/core. 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/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:30e25915-ef1e-5fc1-a06e-308226aad891", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:3ded56b9-c4b0-55e9-bb9c-883de9437c8d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.16-tuxcare.12 of @angular/core. 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/core@7.2.16-tuxcare.12" } ], "bom-ref": "urn:uuid:75c7e79a-a7df-53c8-aea4-162b90cc4ed5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.16-tuxcare.12 of @angular/core." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@7.2.16-tuxcare.12" } ] }