{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:3f60fa4f-99e4-5c4a-9bc1-e91a496527d6", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/upgrade", "purl": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13", "type": "library", "bom-ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13", "version": "7.2.16-tuxcare.13", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:44ea633f-8f10-581b-8504-4b9d16feeaa9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:f9e11c17-2264-58a5-9c4f-217ba07ced0e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:c2ea4d62-0931-51ba-aebd-f3b5c4d8ee4b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:715640ac-0972-5f4b-b73a-86f380346fc9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:bfde68c7-7661-5c31-8a71-c9310c2bd5b3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:daaf3ace-943d-5fd0-939a-67e2722525c2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:e26599cd-2869-5d2c-9b2c-94a5a9b3f09e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:0327ec2b-3e1a-5954-951a-039b727a7f98", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:1dafafb0-da85-5eb7-a8b4-6b0c28c6bb53", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:ca0d386b-fdb9-5627-884b-399756b47d28", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:8673565a-9ec1-50f2-b281-0ece944a1014", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:1d064731-09f0-53ec-aad1-5c97b2e55aea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:97ba0730-9a9a-50eb-b977-a05334f61ed4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:8a657b38-b3d2-5f6b-be7e-91be6670cc27", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:c9db6de1-fb85-5227-bbe4-85db77f6cd4b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:be109506-467a-5f6f-88f7-a268a4cda16e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:a28232bd-845e-55d1-9c27-ac7f2470584b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:84fee645-d6e6-5386-b21c-5bda8795dda5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:7cb6908c-1676-507a-a141-98265b5e0cf4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:b7bd43b7-723f-510d-aa6c-dea21fcd4ac7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:68f6d19b-6b05-5fa9-bbdd-455dfd720d4b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:b03bab4f-0b0c-5f6a-844a-9ef94d09bb49", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:2a734c6f-abb3-5399-bdf0-73307c014e14", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.16-tuxcare.13 of @angular/upgrade. 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/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:57fb3ad1-97b3-5a7a-b2cd-de19f0c39090", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:92d27db4-55c4-5924-982e-5cebe68c8491", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:3f5e4cc0-2369-5b57-89c2-b3a57c966be6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.16-tuxcare.13 of @angular/upgrade. 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/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:1abf6283-8ac7-50da-9033-92ea2c08a082", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88057 does not affect version 7.2.16-tuxcare.13 of @angular/upgrade. 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/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:c1763e99-ce23-59d1-b763-d878657b8654", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:e1a65ba6-67fb-58f0-8460-2d22d9ac6694", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.16-tuxcare.13 of @angular/upgrade. 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/upgrade@7.2.16-tuxcare.13" } ], "bom-ref": "urn:uuid:84a2b69a-2b91-58ee-b77c-6b10d2146d0a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.16-tuxcare.13 of @angular/upgrade." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.16-tuxcare.13" } ] }