{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:47a3906a-b2eb-562a-b0d2-4371f52e6d63", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3", "type": "library", "name": "@angular/bazel", "version": "17.1.0-tuxcare.3", "purl": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:f1e595f0-d8be-590c-8f1f-0b030094e7bc", "id": "CVE-2017-16009", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2017-16009 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6d4ee839-ba60-5001-b2c0-09d44b48eaa7", "id": "CVE-2025-59052", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59052 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d9bddf16-c375-5de9-bb08-3292ecc3b164", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0c41f787-507e-58a5-8d59-a466326bcf87", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9633c595-2851-5f27-a7e0-20877ab46d8d", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1b99645e-96bf-5005-88ac-7064658e2127", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c06fa2f3-59c2-5caa-9ce6-2716996a14f6", "id": "CVE-2026-32635", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-32635 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:fadc263d-63b4-591b-b0cb-3536ab6e8947", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:dc9927ae-d573-5274-b6df-f959e2a10058", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f551e86d-c450-5b4d-beb4-69c50cfa53cf", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c3c8bd85-eb54-56aa-a913-b2b5f72f5602", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:015e6b17-2856-54fc-9e93-54fd4a3b3122", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f16208e1-0778-511d-8f5a-828ccfb24ffa", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:740a34e1-5893-57b8-b162-5da8cec99459", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d008c666-016b-5823-bdf3-0c8672c54d4e", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:cd697e04-d34c-541f-b7eb-2c4ad47bb7d5", "id": "CVE-2026-50556", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50556 does not affect version 17.1.0-tuxcare.3 of @angular/bazel. 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/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5969fb41-3102-556e-b36d-06d305fe0e20", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:47cad740-531c-56ef-a290-f207215b6b6f", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:66822a7d-9d7c-5d87-83ef-c7604211a8c5", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:eb19e60e-975e-5148-92d2-cda191c9d26b", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 17.1.0-tuxcare.3 of @angular/bazel. 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/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:25779221-5b0d-5a19-a49a-eea2fc7f3731", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:76499001-5f82-5cf3-ab1b-d71a6f080104", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bfb541eb-11e7-51a9-8d58-ff4e9f032efe", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 17.1.0-tuxcare.3 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@17.1.0-tuxcare.3" } ] }