{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:32add177-6cb2-5227-a15f-9bc20c405b3b", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/core", "purl": "pkg:npm/%40angular/core@7.2.11-tuxcare.3", "type": "library", "bom-ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3", "version": "7.2.11-tuxcare.3", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:fe61c169-cacf-576a-ba9a-6c43b85f7e84", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:df1d3e0c-09f7-5a66-8903-8654160be111", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:9dd6e8a8-6b16-5acb-9b4e-9383282f0c2d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:e739e2c5-0460-556c-b5ad-002f4b7f57e3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:24634e41-42f3-5bbf-b35d-1c46d99aad70", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:f0765e20-502c-5086-83d4-af2bd5e46544", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:09f0f558-2892-5349-8880-5d270808aa78", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:3a4598bb-9acd-58d2-9e2d-04f610fda28d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:44700231-1f2e-58ba-9f89-384a0abdd07f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:8f99c268-16ed-51c6-a0f8-de77ef8e8551", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:42c9a07d-daaf-5784-985a-f03e573e952c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:765ffe32-e876-5be4-ae34-cba9590e4c73", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:553b6616-9787-5580-978b-267aac58e3c0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:bd7ea67a-72e5-5166-9ef2-dd3a113985e2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:e726ca5a-47a6-58a4-91ef-c4ee31324a9c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:821d1196-c801-5d8a-802f-ed13ce2113eb", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:98d3c9ee-f7c5-503a-91ee-9eda3e39573e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:b98dbf60-d374-5802-b28c-d75a9f8d602d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:fa1b60f4-dca7-5ea4-8906-c4ad8e518a13", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:ca1298ba-c013-53f9-8959-c733fe01c86f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:64b8e7e9-27a4-5c12-87fb-d3bff1181319", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:6381cf51-0a42-5b8a-9ddb-32903ff3f318", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 7.2.11-tuxcare.3 of @angular/core, and is fixed in 7.2.11-tuxcare.4." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:3a63b8ec-b007-5e7f-bf55-765b93f086b7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 7.2.11-tuxcare.3 of @angular/core, and is fixed in 7.2.11-tuxcare.4." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:52d0a51c-b899-5b54-b705-d745f6cd94d1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:8db328fc-b5c4-54d9-a430-e1cbbf016b19", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 7.2.11-tuxcare.3 of @angular/core." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:8850f9d1-56f7-5ac6-a7dd-c1e3529cdea2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.3 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.3" } ], "bom-ref": "urn:uuid:272e186e-5f88-5d49-a04e-1667bbd01d3b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 7.2.11-tuxcare.3 of @angular/core." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.3" } ] }