{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:a4471222-60ce-567e-9634-b88e232c38ae", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3", "type": "library", "name": "@angular/core", "version": "17.1.0-tuxcare.3", "purl": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:28d93d38-abf4-59c9-9767-56689bbd0f3a", "id": "CVE-2017-16009", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2017-16009 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:95f43884-7b77-5ef7-a27a-f1468b008b0f", "id": "CVE-2025-59052", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59052 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c7dff10f-e639-5550-bd50-02ca32f5f63e", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c50c09c1-2a97-5533-95c3-06a62dcc7d6b", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:729e2fe7-7363-575f-b8d3-dca55a6d0e4e", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:61660450-888e-5b24-8179-c5f667696b73", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6c8975df-c777-5b00-aba1-31e6be1f8114", "id": "CVE-2026-32635", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-32635 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1d60311a-872f-544c-a131-212722aed982", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b0b25dd3-acbd-596d-ae1a-cfd9b3faf257", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:69b50254-796f-5704-9772-58aed2c6a4f8", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1c924cb9-dc0f-5fe5-aab0-5ff1ccc1f1a1", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f9b0591c-63f1-5be1-9642-4f7982e028a3", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d7c89726-bb36-5403-867d-297f859d4f65", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:58f4b01e-fdda-566b-9743-7441281c12ad", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:92f3ec61-4faa-54b5-9e30-b345a20c7568", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:17678049-cc7d-5478-846f-599d1ec4e4cb", "id": "CVE-2026-50556", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50556 does not affect version 17.1.0-tuxcare.3 of @angular/core. not_affected \u2014 The Angular repository source code is NOT affected by CVE-2026-50556. The vulnerability exists in the external domino dependency (lib/NodeUtils.js), not in Angular's source code. TuxCare's own patch documentation explicitly states: 'DEPENDENCY fix, NOT Angular source' and 'domino is external/runtime (not bundled)'. Angular's code only imports and calls domino's API but does not contain domino's..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:10a4daba-3d1e-5a49-b89a-12e44dceae40", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b3cf7250-8df3-5fa5-90fa-0d5c6eb4e2b5", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:fab4a203-9008-5433-97d1-b446bed0ca1c", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2f3b9c12-5556-52e9-872b-44773d93bd1a", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 17.1.0-tuxcare.3 of @angular/core. not_affected \u2014 Angular v17.1.0 does not have the TwoWayProperty IR operation that is the subject of CVE-2026-54265. Two-way bindings are desugared into separate property and event bindings before template pipeline processing, with the property half using the same parsePropertyBinding() code path as one-way property bindings, which are properly sanitized." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1ecf92fd-cbd4-588c-91ab-80f67b3910af", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:cd92f682-5cfb-5d8f-bd87-df282507a196", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5b8e139d-19c8-5031-a759-9ec62af083d7", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 17.1.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@17.1.0-tuxcare.3" } ] }