{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:35e5cf5f-6bd5-5f9b-9f94-84d5b963d299", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/core", "purl": "pkg:npm/%40angular/core@7.2.1-tuxcare.5", "type": "library", "bom-ref": "pkg:npm/%40angular/core@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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:48a5edc0-28e4-50b6-b044-2300cb98f1ef", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:7fc905de-e6e4-553b-ae16-0b3e07f8588c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:24feff66-3410-5562-81e9-3951deb8624f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:f1b5fab1-c976-5f64-b14f-4b1beedcc97e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-101895 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:d4c7559b-3584-5734-85da-f8e393eeb716", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:442e5f3c-3b94-5599-b9fa-51c8d826eb42", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:485ee1cb-371e-5173-b255-567b34ebfff1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:3e579550-01f1-5bb2-88b1-f2bdf25044f5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:178f83e9-c5f8-5d8c-b025-29a9f827bc20", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:ecc784bc-2df7-570d-a5c0-65ed8fb78733", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:9ce8dec2-e2b4-5f7c-8082-7df1a79b449f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:2dad5a28-c3b6-5af5-8cea-fc26171bba59", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:521e18d9-7a87-59d1-ab92-d42c7d2dd774", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:673b9481-62a5-56ea-b880-f6dc6859fe99", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:ec83a9cb-fddb-5fda-bd24-d54474b50383", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:8a69f412-e5b7-5173-ad0c-e6a3f027f7aa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:e12a09af-6765-5370-8e0a-428f6d724f77", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:e33404a2-5bd6-5bae-8465-b1e7eea9c2e9", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:b838f5ec-da69-58f8-a4dd-e26a734c986d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:3d46e81a-45f2-50ed-ae3e-4056c5aaa6d5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:2d2681d1-2329-54eb-9909-ed29ff2f9513", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:a16f1a30-dd15-568e-b833-6f43f8f56d39", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:58ba7fba-a541-582b-b377-19430e9046c1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:9b399a07-186a-5362-9e5d-ad72787a4d64", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:6658c560-8f92-525b-8c58-9ef6da7a9af8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:cebc1845-bdb9-589a-98a5-95283a533a93", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:2db3ca80-af40-5971-9a6a-aff425136179", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:547096c1-1cab-5a14-93b7-e71d40c009a4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.1-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:3962ae1d-10b3-5888-9fef-0a23b48af843", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.1-tuxcare.5 of @angular/core. 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/core@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:9b73589f-0f06-573d-914b-000bfc02be3a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88060 does not affect version 7.2.1-tuxcare.5 of @angular/core. not_affected \u2014 CVE-2026-88060 describes an XSS vulnerability in HTML serialization when rendering user input within `