{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:7f8c474a-8a44-5bad-ba8d-9ec2f7fe2fae", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8", "version": "7.2.11-tuxcare.8", "pedigree": { "ancestors": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@7.2.11", "type": "library", "version": "7.2.11" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:715f87f7-74c9-54c8-a975-522d12cb03ff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:394ec5f6-b5e6-516f-9f0a-3e6b0af09d17", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:3e2b0a8b-f908-54fd-a5c6-120b4dadfed1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:c7525ca8-a786-5800-90f3-c3d4f01e7c56", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:086eff37-0fb2-587c-8ce5-bd5e6174cca4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:2feb95ba-34d3-5ec1-98dc-e29f8bba7e1c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:2f633069-f3d8-5937-965a-7e624d30373a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:9f60c60f-ae18-5c67-8292-212fd653b50a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:6765e849-7ce2-5ac1-b5e4-b5ef3d97c3ba", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:e6cd84d6-64d2-5766-8344-781e8d680467", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:cecd1fa7-e039-5ee6-923b-fd068343b0a3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:3859a9be-3cce-5d25-9cca-b429748271da", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:2a9b0424-2bd3-53eb-bb53-9727309b9618", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:3000fd3e-9639-5b9b-9d4d-c0e6313809e2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:ce58c2f0-1d0f-5000-a1e1-08dcb33fba59", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:3bef3fb5-0e41-5f51-903d-0da0dbaf1aa0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:ac2dface-bbdf-5c80-b520-66d113a8ac1b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:4a265455-5645-5e7f-bf4e-157706f63bb4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:49e60c95-1660-5c2d-a9f3-d0bba6c20146", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:4d312f05-98fd-5f0f-992e-a911087b0806", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:63956bc1-7b0c-59a3-9afb-ca4a8d14483d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:3642e687-3abb-5806-8c19-0f1fac95b4e9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:885e23ef-784b-5839-bf6a-f25ec3b0fab7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:07a69129-9844-524d-9f11-ea50bb6249fb", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:195eedc4-66e9-5cdc-81d3-b1001465bb25", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:759ce85a-4b30-52e4-adb7-6bc1d081990f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:1df608ff-3dbf-5bea-8ac8-ef5c7220c825", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:33542bec-798e-5452-b79c-6bc557a0b9ff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:26d81004-9bcd-5143-a3f8-0e82a9d7bae3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:f430a4c9-f6fd-56df-8b90-434624ff6108", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.8 of @angular/bazel. 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/bazel@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:615c6bec-54cb-53e0-a222-bd5a750e9fa9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.11-tuxcare.8 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.8" } ] }