{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c3b0dd93-4069-5620-b2a0-e976fd802c32", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3", "type": "library", "name": "@angular/core", "version": "12.0.0-tuxcare.3", "purl": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:1dfc4977-4d0f-5524-93c6-73a925eff77f", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:01e5241b-8b48-5968-8f67-145e064d3e56", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8baca680-d0e5-59a6-82de-06efecf4de35", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4e276b8f-bcc0-5fe9-bb0b-f6174d8ef1b1", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:429dab39-cb82-578f-8355-a4ebd956cedf", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 12.0.0-tuxcare.3 of @angular/core. not_affected \u2014 The target repository (Angular v12.0.0-tuxcare.2) is not affected by CVE-2026-41423. This version uses Node.js url.parse() for URL parsing, which does not exhibit the hostname override vulnerability. The CVE affects Angular versions 21.0.4+ where the codebase was refactored to use the URL constructor with a base parameter, allowing protocol-relative URLs (//evil.com) to override the hostname. T..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:75b12f5b-f603-5d98-ae35-181a768ff9b8", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d69651ef-92ac-542b-a276-ed50a1d715b2", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4d0f82c8-eda2-5e86-9535-9c269e04e3a3", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:16582be6-f390-531b-8c0e-1574d74b0500", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 12.0.0-tuxcare.3 of @angular/core. not_affected \u2014 Angular v12.0.0-tuxcare.2 is not affected by CVE-2026-50170. The HTTP transfer cache feature that contains the vulnerability does not exist in this version. The transfer cache was introduced in Angular v16+, while this is version 12." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:006d93ba-edbb-5572-979d-311463accd9a", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ca7dcb45-8554-54e0-84eb-de9ad87d3aa4", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4cd52c42-48cb-527d-90bc-0fb97118ac0e", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e29f2b50-f44a-5c09-bb5a-e9c297132ba4", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b2b82c6d-46ca-5b92-ae5b-e17b95c67f2c", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4fe1031c-b618-55ee-bd4c-7bae3c0cf150", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:27d5585c-a34e-5221-a4c7-2d0a9681525e", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 12.0.0-tuxcare.3 of @angular/core. not_affected \u2014 Angular version 12.0.0 is not affected by CVE-2026-54264. The service worker's AssetGroup class does not preserve request headers when making network requests, including on cross-origin redirects. Version 12.0.0 predates the architectural change that introduced metadata preservation (including headers), which was later found to be vulnerable in versions 20.x-22.x." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:de894be1-88e1-5c4e-aaee-a9d9032d2ff5", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 12.0.0-tuxcare.3 of @angular/core. not_affected \u2014 Angular 12.0.0-tuxcare.2 is not affected by CVE-2026-54265. The vulnerability is specific to the Ivy template pipeline architecture with TwoWayProperty IR operations (introduced in Angular 20+). Angular 12 uses a different architecture where two-way bindings are desugared at parse time into separate property and event bindings, and the property binding is sanitized through the same code path as..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:11af3d5f-3e6e-5818-b0a4-b09d11fa49f6", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 12.0.0-tuxcare.3 of @angular/core. not_affected \u2014 Angular v12.0.0-tuxcare.2 is not affected by CVE-2026-54266. The HttpTransferCache feature containing the weak DJB2 hash vulnerability does not exist in this version - it was introduced in Angular v16+." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1485d2bb-9a1d-5fe0-935f-2845ac3acf73", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:59e76718-6929-5a4f-b2fb-9bbd524258fc", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 12.0.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@12.0.0-tuxcare.3" } ] }