{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:02864793-5041-588a-a4e7-67c26e4f2036", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4", "type": "library", "name": "@angular/common", "version": "7.2.11-tuxcare.4", "purl": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:36679059-0211-5d87-b18e-e8467e7fd524", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:80f3840b-cbe6-59af-89b6-5d794027b239", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:df85e8d2-0f62-5e8d-95d1-d81a02ce5d83", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d1664454-b112-5bb9-8555-cf9dcb84bbf7", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:caeb7a77-ca63-52de-930a-eb225d0ceaf0", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9d4ff6a2-2187-5c85-ab9a-bded1704b761", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6de6076d-cc2d-5bdc-b3ac-e0054a25a726", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e1d3ceb3-e972-5f47-9489-232ba3a098a4", "id": "CVE-2026-50168", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:859478ef-6ac5-5ecf-9461-8b42222cb5b7", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:167d6bad-8c13-52d2-8a5d-630e3daad48a", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a3a1d76b-5041-52d4-953d-6b6bcd1836ff", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:33d39802-9ef6-5348-ac35-666e28a45cea", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6c2d05dd-b61f-55a3-a1e4-24e02498c206", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:030965bf-5e94-50c0-9a7c-c80d5cf26a35", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:09dc64ed-b148-580c-8309-0dc68079ff8c", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ebcd2a57-1346-50f5-accb-6c0fc2729073", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:42edda29-9ea5-5642-8d30-b7e2c5478314", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:22e6ee20-82f8-50cd-a3a7-f02229436b78", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4e5b1886-fb0b-57f5-8f8b-98d684f3a044", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:09ca607e-c89b-5108-bc7f-66b677193fad", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d8c65dbf-8ad3-5cfd-b83a-019861598698", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:678d3307-e391-570e-a410-d578552b480a", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:302c58f5-7eba-5956-a84e-0e567e48e559", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cd567b69-85e3-570c-a0df-29bd61217679", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/common@7.2.11-tuxcare.4" } ] }