{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:b1c3dac3-d5cf-564c-bbfc-e7c0af44c440", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4", "type": "library", "name": "@angular/core", "version": "7.2.11-tuxcare.4", "purl": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:7c47937b-aa02-51f9-9e3c-75e325b9cf65", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:482afc3d-6dbd-5f77-a3c0-c329694e8a3c", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3ad228ba-77fc-5a47-9ed8-3bc9c8a508dd", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b7f65ec5-30c0-5c68-b771-b29041b1bd2e", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1f21f2b3-968b-5106-99af-c2b52228e08a", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e8e595fa-cd26-5f33-a3cc-831f97c12b24", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2bb89441-4818-52eb-9856-672f740f287a", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3db64977-b153-5626-9769-68147ab00207", "id": "CVE-2026-50168", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.4 of @angular/core. 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/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4f51a90f-189d-5545-976e-5842d00ad2a5", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e6431aca-c771-59b7-8181-b1bb90d9e424", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.4 of @angular/core. 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/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:46949373-225a-5313-ba3a-04d32ce672ea", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:74e3aeea-cb56-5655-bffd-dfc56a2a6797", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7114fb63-6f93-5d24-ae68-f5c01f6ebbc5", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e6cdf0fa-09a3-5e36-abd0-6d5b5926bdca", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f5673d4d-ae9c-52c5-8714-78ca3dbb403b", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f7497f38-ca6c-57e5-bac9-401e785a801e", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:11d5264b-1481-5520-9e8a-77e1f1ca9294", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.4 of @angular/core. 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/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5e398dda-36bd-50c6-ba5b-84974cd9cbc2", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.4 of @angular/core. 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/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e54221ff-5324-563e-99c5-aa1b02c3510d", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.4 of @angular/core. 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/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:72282867-0030-5d3a-8683-287f404a641e", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:14bf07c8-e496-5ba0-94eb-e60466992aae", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a4b0fede-3a93-5652-ac4a-c17498979ed5", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.4 of @angular/core. 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/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:63fcf79d-ea0f-5467-bf29-0c9fb8652d3d", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:571701a0-c3f6-5953-8dca-4178b4a90c0f", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.4 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@7.2.11-tuxcare.4" } ] }