{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:eb9a6a17-cd95-543b-9e79-43ad38b1b4fb", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/http", "purl": "pkg:npm/%40angular/http@7.2.1-tuxcare.5", "type": "library", "bom-ref": "pkg:npm/%40angular/http@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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:0ea061ca-5311-5d6d-b16f-23b1a53dadf5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:91a4bfcd-4678-5fc5-92e7-f651425370ff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:6f265a21-d0c0-5453-a643-ed0ed025cfa9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:1fd79e3c-bfea-5d29-abe7-d451ec64ccaf", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-101895 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:f9ae8882-cb71-5b22-831b-563fc5bfa73e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:f1596c47-714c-59a2-827d-0f3fa52cfb14", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:71753ca1-7715-56f0-b14a-9b5eeadde7fa", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:ba5191a5-02ba-54b0-ad86-ae0e85c2ee7c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:32796c6e-af15-5415-9fc3-30905604e0a4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:03b5147d-4dd0-5be9-8823-3a424b55beb9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:67a1917e-4c05-5837-b25c-a05c1a458ceb", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:e49a7151-0596-55cd-8b81-0290bef93d44", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:df327b61-f6a5-55c7-91c2-ffd30ce8a534", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:dfc572a3-5f79-5549-b658-78d835de33e7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:a55b0911-8ed9-5f76-9c90-193ca9f78a97", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:27607b4e-356f-58ae-a266-d78a8580ba63", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:b76a4f8d-37ce-5e37-95bb-5b8ee8105d2b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:22d64232-0a0e-5b94-a4d7-4c71400cdf8f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:8886bfde-e3a8-5f49-aef2-b11b1e296ce9", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:aea2f70c-592b-534d-a6b5-29db92f56b56", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:cd4a92e6-73a5-5dd9-a5e5-411e7e1e7de4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:d1d89b06-c968-5e2e-969b-46f67d2e8404", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:9fb47f07-fd73-5d4d-9242-653b20a2cc4e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:037829b9-84e9-54cf-a8f6-d585f747460d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:e3279b10-dcb3-5394-9549-af83aad6b875", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:6c9ab8c0-b89d-514c-934e-39aa82741326", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:03f2952f-2c1a-5c3c-9307-d03b7dd77b04", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:6c84a552-b906-590c-83fd-39e3573d84ac", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.1-tuxcare.5 of @angular/http." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:2722620f-f0e7-598a-8220-ee9e8f965748", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.1-tuxcare.5 of @angular/http. 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/http@7.2.1-tuxcare.5" } ], "bom-ref": "urn:uuid:f7b9a608-1669-5443-9efd-f758ee7d85e4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88060 does not affect version 7.2.1-tuxcare.5 of @angular/http. not_affected \u2014 CVE-2026-88060 describes an XSS vulnerability in HTML serialization when rendering user input within `