{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:0f6106dc-40ca-57c5-bde8-673a5f7f5812", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/core", "purl": "pkg:npm/%40angular/core@7.2.11-tuxcare.6", "type": "library", "bom-ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6", "version": "7.2.11-tuxcare.6", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:39e8817a-51e7-548e-a15b-db09b53a425c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:ab1bbcb1-2712-51d8-b0d6-29f54a944743", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:b1811894-4feb-50d5-8814-fef3176544e9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:d1fdf9b9-72b0-5ffd-9f58-8e84acfabe82", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:171e15df-79c0-5eae-9dca-f37a8bf53aab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:9eca8e28-8877-55ec-afe9-7fa115bf44d0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:1b49f973-d5b6-5b71-b6a8-66c86d1d908c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:fd91ba5b-cd13-5957-8b14-0b478da95543", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:d4bf7411-d288-5f44-804c-341a41c542f0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:38d99fb6-e262-54dd-921d-49a0863e6874", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 CVE-2026-50168 addresses vulnerabilities in the WHATWG URL-based parseUrl implementation and allowedHosts validation feature introduced in Angular's CVE-2026-41423 fix. The target (v7.2.11) uses a completely different architecture with Node.js legacy url.parse() and does not have the allowedHosts feature. The specific vulnerable code patterns that CVE-2026-50168 patches do not exist in this ver...", "justification": "code_not_present" } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:423120c5-4b95-544f-90f2-c8061c68f928", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:e3712515-eb5a-51a1-b523-b52c045d02e2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular v7.2.11 is not affected by CVE-2026-50170. The HTTP Transfer Cache feature that is vulnerable does not exist in this version. The feature was introduced in Angular v16+, and v7.2.11 lacks the transfer_cache.ts module, withHttpTransferCache provider, and provideClientHydration functionality entirely.", "justification": "code_not_present" } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:0e2e33ab-c203-5b5e-87fb-0c33123d4fb3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:92b12b9f-3a52-5f60-b591-4247c4562a9d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:291da4e3-0503-5d1f-b5af-376babe5b36e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:64cdc8b6-5c42-5453-8d07-12ceb57cb47c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:62364ee8-aa0b-560c-9d03-9feb4c1f482e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:6312550b-d6d0-5e30-9f7e-cdb2fae19f94", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:401153d2-883a-5fd8-84d9-09d2c4ddf1b5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular 7.2.11-tuxcare.2 is not affected by CVE-2026-54264. The vulnerability concerns sensitive header leakage on cross-origin redirects in the request metadata preservation feature. This version predates that feature entirely - it strips ALL request headers when making network requests for assets, as evidenced by code comments and the absence of the newRequestWithMetadata method introduced in...", "justification": "code_not_present" } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:e3661224-adf9-5535-ba22-251a0e721197", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular 7.2.11-tuxcare.2 uses View Engine compiler architecture, not Ivy. The vulnerability (CVE-2026-54265) is specific to Ivy's template compiler pipeline where TwoWayProperty operations were missing from the sanitizer resolution switch. View Engine does not have TwoWayProperty operations; two-way bindings desugar early in the template parser to the same parsePropertyBinding() code path as on...", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:35855151-0f96-5c35-bf57-de4fed745ebf", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular 7.2.11-tuxcare.2 is not affected by CVE-2026-54266. The HttpTransferCache feature that contains the weak hash vulnerability does not exist in this version - it was introduced in Angular 16.", "justification": "code_not_present" } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:dc03dabe-b71f-596e-a73a-959fa10f10ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:bcbcba38-c5ae-54d1-93f3-506e0876db94", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:5ac539b2-e380-53a7-9a99-0daa7e634a76", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular v7.2.11-tuxcare.3 is NOT AFFECTED by CVE-2026-68945. The vulnerability affects Angular's `HttpTransferCache` feature, which caches HTTP requests during Server-Side Rendering (SSR) for client-side hydration. This feature did not exist in v7.2.11 \u2014 it was introduced in Angular v16. The vulnerable file `packages/common/http/src/transfer_cache.ts` is absent from the target SHA (8c4c3a453736...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:f5377771-80cd-58ee-b8d8-947c8b07a646", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:14315776-899a-505c-8078-ea8e3e16f01d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:f0a03888-0912-5285-b9fc-f7bedd42b1e0", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular 7.2.11 is not affected by CVE-2026-88056. The vulnerability requires calling String.prototype.trim() on URL strings before WHATWG URL parsing, creating a discrepancy that enables SSRF. This vulnerable code pattern was introduced in Angular 14+ with a new url.ts file containing parseUrl() that called .trim(). Angular 7.2.11 uses a different parseUrl() implementation in location.ts that d...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:43069d16-be11-5c91-9e7f-fc4d91e3cc8f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:478f51bc-39af-5369-ab88-454368d20411", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:378e9d61-0b18-57a5-897e-6bff4bd053e8", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.6 of @angular/core. not_affected \u2014 Angular 7.2.11 is not affected by CVE-2026-88059. The vulnerability requires HttpTransferCache interceptor and hierarchical HttpClient configuration APIs (withRequestsMadeViaParent, provideHttpClient) that were introduced in Angular 14+ and do not exist in this version. While TransferState exists in 7.2.11 as a basic SSR state transfer mechanism, there is no automatic HTTP response caching to T...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:6c330fc9-075c-5eb3-b6bf-3267d000a7c0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.11-tuxcare.6 of @angular/core." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.6" } ] }