{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:85016377-ce47-57f9-8495-73929106a255", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/upgrade", "purl": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6", "type": "library", "bom-ref": "pkg:npm/%40angular/upgrade@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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:e1d4c4e5-e525-5d4d-aa85-8a84ed9a14ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:5ee30ecf-4c4c-58b2-afa1-c7e9b75353ca", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:4f00c9a7-9b62-533d-b8c4-302a426a3c59", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:ed2835c0-e450-52a4-b89b-b801171ae4ca", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:4e2b22d9-e1d2-5722-8054-d88bc4cc372b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:e2ded547-09bf-5d66-9649-b935800989a5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:f3075a98-09fb-51e3-ac8f-55dc53e2c825", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:beb3d273-5d90-56c1-b53c-c57e479802f8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:9a9df11a-d419-54dd-a0ac-a5abbf6128a1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:20fcdeed-d249-5adc-bbcf-7fbfc4184239", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:cc77083f-5783-53d5-9756-ff6d41c9440b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:b2731e5c-550e-5f56-9667-d956b7b2c40f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:910f0f68-d186-589d-8343-ec79f44fa026", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:047a67af-146c-5596-9518-c2607dbb5111", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:8e349ed4-a1d7-5941-908c-16acd0b7bbb7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:e836ee82-da80-56ac-a418-498f4ea69687", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:ee1614b8-763f-5ff3-a7c9-0b7547850ca9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:b91819bb-3625-548a-994c-1d54a2e9beb1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:d5aeae11-ba97-5313-a32f-c6bb242750e9", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:15a3d936-664a-5465-959e-c120e0f813a8", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:e6a8ac73-9cfd-5aa2-8376-f8c09348335b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:33a460cf-8a3d-5d29-8c25-fbe4e8b1e3f6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:33db84ff-0740-59f0-8993-03bcddc280f6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:803ba79b-ff05-5940-9cb4-db986938077c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:748d4663-f728-5da8-b87a-cea2668a7445", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:05114a56-2c07-5998-8547-2a68c3b887e0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:7a01394d-3316-5ada-a185-99ff31d1a9a4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:0c3510fe-2004-5563-9720-3ed78e69619b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:41ce981c-47ee-5730-83e7-67860dafdb72", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:fc38f163-9684-5cd1-8dbb-343b671184a5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.6 of @angular/upgrade. 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/upgrade@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:767d7337-cf78-5da6-a1be-83f11615cc8c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.11-tuxcare.6 of @angular/upgrade." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@7.2.11-tuxcare.6" } ] }