{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:7726c15f-046d-54cc-8847-7e1bf17d343a", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@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/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:ad0db121-780e-58e9-b3f8-546fd6c257e7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:db6a922f-adb1-5be0-a41a-72b0b780e51b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:93b00735-0d73-56d0-aee3-92246c08dfc1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:550bf4fe-4631-576d-8815-7a0f9989282b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:481fe837-3c35-5cf4-8927-af96d13bccd6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:ba16dbd6-fd5c-5d78-bfb8-61d1c5d0ea32", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:2c856a33-11c8-5316-874d-fc766e99cf1c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:405cf40c-212a-5520-a314-a8226d87069c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:16b40d38-285f-5e9a-8644-986c44af98d9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:cbcba65e-4ecb-573f-85e0-fae112b985f6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:3178612f-6eec-5ba8-bd58-c587b3e16b5e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:d826ea54-e4a2-5b09-913a-dd7e11bffc7c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:5f863ddd-00af-5c0b-9cbd-c1601d1aa04e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:27cb1c67-0ffb-5368-b72f-768b22d7ad27", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:5be817ef-83ea-5509-b5ea-74b4bbb3324b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:aea2b338-25d0-5f54-a87d-8a95d05e88e4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:56cafafd-ba8d-5d4c-a898-9abbb3768b06", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:c65df425-30db-516d-9c45-f54a2c0b71f7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:6a7fdaa1-f9b4-53e4-99c4-2f36abde4f55", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:3a053384-b6c1-56b3-a38e-a60c06211fae", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:a9632c25-cfb4-5af8-a192-eac4f914460a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:a29511c7-f7c5-53f6-b8c4-e9693ff3a860", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:083a0eef-5a30-5742-b17d-5eba924cddd3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:147bd8cf-eb1b-564c-bf62-2c4f96d7631a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:32a96e50-daa3-52f0-b420-9261ba15e6e0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:7b8564d4-0767-5c86-a136-9f591ffedd01", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:67316aeb-602c-5c76-9a7d-5f0959dd4534", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:4c43adaa-4ff0-52d3-ad0d-7fc31866f4d7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:d6f2f444-db94-5e39-bdce-615d3f9f6ea3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ], "bom-ref": "urn:uuid:c37699f6-8bcb-5552-b61a-239fc1ae35c1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.6 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.6" } ], "bom-ref": "urn:uuid:baf4e21f-6744-5f78-bcda-c485aaa4f21b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.11-tuxcare.6 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.6" } ] }