{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:6f4b601e-94be-5d79-b541-e89f290f8161", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4", "type": "library", "name": "@angular/bazel", "version": "7.2.11-tuxcare.4", "purl": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:e1785db9-8da4-50b2-98d1-5f53503d6bab", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:702020a9-c2c5-5b58-8bd1-9fd406622159", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:78342888-3a45-562d-b3d2-f76e2a41555a", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dacd8a07-1497-5825-a0a0-cc7d41ea2a48", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5c9187cd-dbcb-5749-83e5-86bf664b729b", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bd3ff1d5-8281-5f29-b381-420825ba952f", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:163a762b-5fd5-5da7-8a89-67741cbbe082", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:005abd10-9d7c-5645-843f-fd92616afd59", "id": "CVE-2026-50168", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c899ea68-c4c4-55e6-822a-db567665a068", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5c4e96d2-e6e3-5dfc-a389-e48b06b85b68", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:506447e7-7f89-524c-a527-025ecb9cdd01", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:619cd65e-11ae-5c90-8d46-1f597d999df0", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dcdd2223-ee00-5896-b66c-606587b377ad", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fd65a0bf-5582-5f43-96e2-180677c74edf", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6ba20685-3a06-5ee2-879d-df92d7bcc826", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f0162e03-9fa1-567d-8890-dac2ba27ac41", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4554c3b7-a1dc-512a-ba38-9135b3405985", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:39a9ef1b-455b-51a4-8f76-785c3bb03b9f", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3f7dc585-9844-5668-a06e-3b4bc7d00857", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:efb85f00-c0f8-5b3c-b019-a4a196fcd35f", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1baf1761-d37b-50e9-8654-d784f703107d", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5c557e84-215f-5964-8522-dac7d5745968", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:089ced71-b9a5-5579-ba02-d0ebaabfa74b", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:945b9c7b-da8a-5346-bb19-a3af2660230e", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@7.2.11-tuxcare.4" } ] }