{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:26ef0ca7-623c-5f33-8e0a-b3482977bb60", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/upgrade", "purl": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5", "type": "library", "bom-ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5", "version": "7.2.1-tuxcare.5", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:f9bdd3d0-690f-512a-a6ca-cc6cbfbd024f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:787625aa-d400-542c-ac7d-c5c992db305c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:898c71fb-5e5c-5c85-a58f-5dc5b12f44b8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:0403dde6-25bf-5764-8db5-760bfc872de1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-101895 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 CVE-2026-101895 affects domino's HTML parser (infinite loop in DOCTYPE parsing), but domino's source code is not present in this Angular repository. Domino 2.1.0 is declared as a runtime dependency in package.json (line 67), not vendored or bundled. Angular's @angular/platform-server uses domino for SSR DOM emulation (domino_adapter.ts calls domino.createWindow), but the vulnerable code (HTMLPa...", "justification": "requires_dependency" } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:57aa0d28-1062-5cab-bd7e-da2664c82bfe", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:febb9f7c-b6ca-5f5a-af04-5427c4511479", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:4c725cc1-9501-5c45-a0aa-7fd60ab67510", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular v7.2.1-tuxcare.2 is NOT affected by CVE-2026-41423. The vulnerability requires WHATWG URL parsing with hostname exposure, but this version uses Node.js url.parse() and does not expose hostname/protocol/port properties. The architectural difference between v7.2.1 (legacy url.parse, no hostname tracking) and v8.2.14+ (WHATWG URL, hostname tracking) means the vulnerability pattern does not...", "justification": "code_not_present" } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:ec68a751-c9bd-5265-b906-88bfd3a55e26", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:536f0ecc-8e4f-5f3e-930b-8660868d2ff4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:8dd2ea34-220c-5997-a5ce-1702bfefe29a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:10d1d331-f4e4-5fc8-8ff9-e1326494b962", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular v7.2.1-tuxcare.2 is not affected by CVE-2026-50170. The HTTP Transfer Cache feature that contains the vulnerability does not exist in this version. The feature was introduced in Angular v16+, while this target is v7.2.1.", "justification": "code_not_present" } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:7c5ae3b0-eff6-590f-b097-99d59be1267f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:c9e401e6-7bcd-51d3-80d1-900b1522df7e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:c7cc3a9e-32f9-5fd3-a943-a8bddd278b19", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:78093492-6102-5be0-9104-d6cd0245c94b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:5e69545a-39d3-5655-bcba-903594159245", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:270f524f-26bf-58ba-aeb2-79cdc151f777", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:5e62f0be-1bdb-53b7-8686-a61f28e1c22b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 The target Angular v7.2.1-tuxcare.2 is NOT AFFECTED by CVE-2026-54264. The vulnerability pattern (service worker forwarding sensitive headers on cross-origin redirects) does not exist in this version's architecture. Asset-group requests are reconstructed from URLs only without headers, and data-group requests delegate to the browser's native fetch which handles redirects per Fetch specification.", "justification": "code_not_present" } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:fce7e0a6-aa90-534c-8a9b-c290a9f63100", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular 7.2.1 uses View Engine, not Ivy. CVE-2026-54265 is specific to Ivy's template pipeline and the TwoWayProperty operation kind, which does not exist in View Engine. In View Engine, two-way bindings are desugared at parse time into separate property and event bindings, with the property binding receiving identical sanitization as one-way bindings through the same code path.", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:e2ca2265-8614-5394-bfaf-c75f4c2a1fdd", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular v7.2.1 is not affected by CVE-2026-54266. The HttpTransferCache feature containing the vulnerable weak hash function does not exist in this version. The feature was introduced in Angular v16+, while the target repository is Angular v7.2.1-tuxcare.2.", "justification": "code_not_present" } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:cf343ad8-56d7-5e3b-9718-63e8988ea5b6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:79110cd4-71b7-5b7b-b12c-ec5c6a7ec6f7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:1c3b0b44-51c3-5def-8351-e97ae81034be", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular 7.2.1 is not affected by CVE-2026-68945. The vulnerable component (HttpTransferCache) does not exist in this version. HttpTransferCache is a Server-Side Rendering (SSR) feature that caches HTTP requests for client-side hydration, which was introduced in Angular v16. Angular 7.2.1 has only basic TransferState (a generic key-value store) and HttpParams, but no HTTP request caching mechani...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:b2609800-7db4-5681-b292-0d423052fc69", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:7d73855b-ba53-5c03-b645-95581da87c2a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:06376bd6-1be5-50ee-8cea-c51f8782c90f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular 7.2.1 is not affected by CVE-2026-88056. The vulnerability was introduced in Angular 22.0.0 (May 2026) when `String.prototype.trim()` was added to URL resolution utilities. Angular 7.2.1 (released ~2019) lacks the vulnerable code pattern entirely: it has no `url.ts` file, no `resolveUrl`/`parseUrl` with trim(), no `relativeUrlsTransformerInterceptorFn` interceptor, and no same-origin va...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:22000849-5605-53e1-b6a2-6a344d6feaf2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:edbc1093-7445-59c4-b501-a637bf30528a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.1-tuxcare.5 of @angular/upgrade." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:dde48ef3-d2ff-551c-b115-9c04754419df", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 Angular 7.2.1 is NOT affected by CVE-2026-88059. The vulnerability requires HttpTransferCache with hierarchical HttpClient configuration using withRequestsMadeViaParent(), features that were introduced in Angular v16+ and do not exist in version 7.2.1. The target uses the legacy NgModule-based HttpClientModule with no automatic HTTP-to-TransferState integration. This assessment is consistent wi...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:10200ab0-0b1e-56f7-a00a-719a93627e23", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88060 does not affect version 7.2.1-tuxcare.5 of @angular/upgrade. not_affected \u2014 CVE-2026-88060 describes an XSS vulnerability in HTML serialization when rendering user input within `