{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:44203fd7-afeb-5841-9d2d-a69c00a6bbed", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/common", "purl": "pkg:npm/%40angular/common@7.2.11-tuxcare.3", "type": "library", "bom-ref": "pkg:npm/%40angular/common@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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:93e76080-341e-5db3-b74a-7b259b91e390", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:5a6d5cbe-c0fb-5858-9024-29c3f0d58093", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:87798252-a51e-5428-b741-393e99437f06", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:d403b3e3-8399-5eb7-be6b-f71099d96431", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:8a05a84d-2d9d-52da-9e9a-e8840fcc3450", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:d944d0e6-5116-5c41-a653-35add8ac8bef", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:3ca984dd-9f23-5823-a251-902f03d1da5a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:4242ab09-54af-5a20-be9a-839156acd468", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:77293729-b213-5bc1-b7e9-3e2fde89451d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:be48da81-8c24-5d9c-af15-672eebb5b803", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:3b818240-f28b-5e8a-9810-1b22051d06df", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:53cc1d67-947b-5953-8371-918552cf3fd1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:b370ad14-0007-5e1c-b1f1-2b15c5c6ad36", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:9e16d6a3-753e-5337-bbdb-8075144536d3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:ac5a267e-e838-5226-ad6e-7c76e1abce64", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:9d0c6283-347d-5007-8ef1-042eecf2d2f2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:6d68ac9c-1fd6-5429-b3d9-528f5eb4468e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:1fc654ff-cdb3-5f88-af18-c0dfa3206915", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:d4dffa97-70ad-5ec0-b431-7893609e5c14", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:acc13ae4-b429-5d77-a48b-ef172819ace7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:c008f0d8-072a-5a33-99d7-acb0521e7e35", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:8b056bd9-2168-51bb-b702-43504eb632e1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 7.2.11-tuxcare.3 of @angular/common, and is fixed in 7.2.11-tuxcare.4." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:620ce898-4092-5e7e-bfb9-96be71eca9a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 7.2.11-tuxcare.3 of @angular/common, and is fixed in 7.2.11-tuxcare.4." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:3b12d7d1-606a-5bb8-86f7-176959cb7080", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:789757e1-53ca-5111-b836-e15004799f09", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 7.2.11-tuxcare.3 of @angular/common." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:3ac95e13-158e-5ebc-8826-9b8cd82617a6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.3 of @angular/common. 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/common@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:c575446e-4ecb-5788-b7fb-df4e789fc0d0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 7.2.11-tuxcare.3 of @angular/common." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.3" } ] }