{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:1cdcc41a-9e5a-5dba-b1df-45770feaa993", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/upgrade", "purl": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8", "type": "library", "bom-ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8", "version": "5.2.11-tuxcare.8", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:59852acf-b354-5949-92f6-8d8f4195344e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:24549c20-5f2f-5129-86f9-2e32275d4cf4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66035 affects version 5.2.11-tuxcare.8 of @angular/upgrade, and is fixed in 5.2.11-tuxcare.9." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:3f142600-74f9-5ace-954f-a809ea95a36e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:7c7886fb-9a0f-5c0a-acdb-6c865f147c6f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:a468bf33-6995-576e-a133-ee13c0d59130", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:34df887d-f862-587b-a216-669769b25c2a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:a61fcf4f-1259-5318-ae7d-e9159fc0f8db", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:9a7275a2-6262-58dd-a226-26f1f161fff5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:34e49cc4-56b0-5c37-ab0f-acc322d1b461", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:703ecbe9-a5c0-52a9-bf5a-0fc0e1e1306a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:0f794c04-d2d6-51de-9883-0e56d911ac16", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:b2e35c70-2d71-5c84-9243-e8da08ff397f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:0ed4742e-11a7-5bde-870c-49d47ce31a7b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:b49f4338-73fa-56a0-851c-0c0eef49eebc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:646e32e3-6c32-5554-ae96-43858662b227", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:6e05dbf0-64d7-52c3-b15c-e291d53d8519", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:98fcd4c4-1ffb-52c0-bcdb-37114e66e3c3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:b8893160-9e69-57e4-9933-8c417a9162cf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:a8d611ca-e1a5-53db-bfb4-37c35ac76e0a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:2a2345a8-6725-5a70-8b74-61953a3fc3a7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:e15dd603-f6de-56b0-93ea-ab11a6d529d2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.8 of @angular/upgrade. not_affected \u2014 Angular 5.2.11 is NOT affected by CVE-2026-68945. The vulnerable component `HttpTransferCache` does not exist in this version. This feature was introduced in Angular v16 as part of the modern SSR hydration system. Angular 5.2.11 only has the basic `TransferState` API (a generic key-value store for manual state transfer), not the automatic HTTP request caching interceptor that contains the vulne...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:89063556-738b-5be1-884b-c3932bb098ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 5.2.11-tuxcare.8 of @angular/upgrade, and is fixed in 5.2.11-tuxcare.13." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:2e15f78b-929d-5347-b018-93ed051b69f1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 5.2.11-tuxcare.8 of @angular/upgrade, and is fixed in 5.2.11-tuxcare.13." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:919b66a3-9335-58ef-8580-3efc7b114cc2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.8 of @angular/upgrade. not_affected \u2014 Angular 5.2.11-tuxcare.19 does not contain the vulnerable URL resolution code pattern described in CVE-2026-88056. The vulnerability requires the url.ts file with parseUrl function calling String.prototype.trim() and the relativeUrlsTransformerInterceptorFn HTTP interceptor, both introduced in later Angular versions (post-June 2026). The target version uses a fundamentally different architectur...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:44947e1a-216d-5faf-8f09-7b4702355738", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.8 of @angular/upgrade." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:6baa7f91-681f-50fd-b36f-8370b0d544cd", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.8 of @angular/upgrade. not_affected \u2014 Angular 5.2.11 is NOT AFFECTED by CVE-2026-88059. The vulnerability requires HttpTransferCache with hierarchical HttpClient delegation (withRequestsMadeViaParent()), features that were introduced in Angular v16. Angular 5.2.11 predates these features by approximately 6+ years and contains only a basic HTTP interceptor architecture with no automatic response caching mechanism. While TransferStat...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:becd34eb-018e-54a0-8026-a44bf9beeae8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.8 of @angular/upgrade." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@5.2.11-tuxcare.8" } ] }