{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:4a280bce-db69-541a-8ad6-154720ce38a5", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/upgrade", "purl": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6", "type": "library", "bom-ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6", "version": "17.1.0-tuxcare.6", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-59052", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:3ecf06a8-707f-551d-8ec9-718d100a760f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59052 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:ea4ff4a4-b2be-5ad3-80e5-ccbfd5993a23", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:65007b45-af4a-514f-a463-6d7c2c0600ca", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:75d4ff01-074b-5ce4-9421-1f1b6493826f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:d6f02ab7-4c9f-50f6-a4bd-8c6e6119a57b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:4a77fa72-748e-5f86-b5c5-9ef35e1a1ff0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-32635", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:b3749ec5-a7d1-59a3-a259-8c9c83e492d2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-32635 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:3dd37ae2-c65a-53a9-99a8-c477e2c84a97", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:6c7bcef5-744a-5689-b8d6-847bc00404ae", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:2f3a259f-3bec-5792-9357-a9ad3688afb9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:02f33308-92c1-5a67-8f07-6e3923b37314", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:f6ed7d08-a339-5ff1-9d9a-6b0a69f6e173", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:6b068f1d-34b6-52fc-bb52-4bfb5c37a274", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:c2a5070b-5372-594c-9b21-ce7976bf66dc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:482a79f2-c9fe-5d72-bcef-52f323591a95", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:d15f60a0-faee-5db2-8ce0-0e1347ff9123", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:dc64c6a3-f19d-507b-83c0-495b14f8ba40", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:2e63bf1e-09aa-5388-87a6-648777346d4f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:7c73f273-be71-5031-9947-2e9f94d6bdb7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:e92e9756-ad8a-5881-97d9-8561a917c4a8", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 17.1.0-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular v17.1.0 does not have the TwoWayProperty IR operation that is the subject of CVE-2026-54265. Two-way bindings are desugared into separate property and event bindings before template pipeline processing, with the property half using the same parsePropertyBinding() code path as one-way property bindings, which are properly sanitized.", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:fd05c6c6-c18e-5808-9ca4-34b7f62d2658", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:9ca88bc3-28f9-5f84-b10e-b93c19812804", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:3c9b0c5a-12d8-51bf-9d9a-6aff9b9f808d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:b94acb8e-5ea0-5f8a-b07a-9bbfe0d72809", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-68945 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:d1ab653c-308a-57d3-9e04-668d53e1c61d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:13118b75-88b6-5ef9-b6a6-9e9e1bc3138e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:3c12b930-96b9-53f8-a10e-67d73a668ea2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 17.1.0-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular 17.1.0 was never vulnerable to CVE-2026-88056. The vulnerability exists only in newer Angular versions (v18+, v19+, v20+ before fixes) where a url.ts file with a parseUrl function that uses String.prototype.trim() was introduced. Angular 17.1.0 does not have this file in the upstream release. TuxCare created url.ts for their 17.1.0 fork (commit e06d36f339 by ejarocki@cloudlinux.com) but...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:e867f1cb-04aa-592b-8fa4-cb4a57050870", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:08b6aee2-797c-57ad-b5dd-51f81981fedd", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88058 does not affect version 17.1.0-tuxcare.6 of @angular/upgrade. not_affected \u2014 The Angular repository (version 17.1.0-tuxcare.5 at SHA 1b802ce320) is not affected by CVE-2026-88058 because it does not contain the vulnerable source code. The vulnerability exists in the domino library's HTML serialization code (lib/NodeUtils.js), which Angular references as a dependency in package.json but does not vendor. The upstream patch (89b20568dfaee1ec8e0b3bcf1872acdddd2f4fef) is a D...", "justification": "requires_dependency" } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:ff457066-3683-58cf-a530-82551c255ddf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88059 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ], "bom-ref": "urn:uuid:b641d83f-a649-5b5e-bc4d-cf819049dc66", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 17.1.0-tuxcare.6 of @angular/upgrade." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@17.1.0-tuxcare.6" } ] }