{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:f871562c-e0d1-5ab1-8f93-03628169798c", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2", "type": "library", "name": "@angular/bazel", "version": "15.2.2-tuxcare.2", "purl": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:3b710aa5-9c78-5b28-bfb9-615a70959283", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:14571220-e99a-5e7e-8ad0-a5025507a4b1", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2e505825-abf1-5985-bea3-1e97bee0b0a2", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:140565d9-dd50-5473-a993-a97b3a05f48a", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f4feae06-7c71-5038-b6dc-0cc2f0e576f1", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 15.2.2-tuxcare.2 of @angular/bazel. not_affected \u2014 The target repository (Angular 15.2.2-tuxcare.1) is NOT affected by CVE-2026-41423. While the target lacks the specific fix from the upstream patch, it uses a fundamentally different URL parsing mechanism (Node.js legacy url.parse()) that does not exhibit the WHATWG URL specification behavior exploited in the vulnerability." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:3c4e8207-fb94-5b90-8fe5-64585bf077c0", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c3f9770c-f78c-5614-91a5-e6c3e9171e34", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5ee1dd1e-109e-52d3-a2f7-26bdcc3cc962", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8de0bc91-a55c-53a8-999f-3e8b18410c4e", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 15.2.2-tuxcare.2 of @angular/bazel. not_affected \u2014 Angular v15.2.2 is not affected by CVE-2026-50170. The HTTP TransferCache feature, which is the subject of the vulnerability, was introduced in Angular v16.0.0 (March 2023). The target repository version (15.2.2-tuxcare.1) predates this feature entirely and does not contain the vulnerable code path." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f92f1fd3-41ef-5f10-a570-48c28ebca752", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4ec8324e-23ab-5a3d-8947-24c0e4d289f9", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:37fe1c6c-8738-5245-bb5a-cd993e78921d", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:242f6370-9e52-5d05-bb79-38d376ac66e1", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a3ca7b50-a931-5f85-8684-31b788f0e12a", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d09a93c4-b989-5bd2-8fa4-4fcb950505ea", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c04db8ff-1232-506f-bac4-779edb39843f", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:266cc5f1-7209-56a2-aa4e-712d18b60bd1", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 15.2.2-tuxcare.2 of @angular/bazel. not_affected \u2014 Angular v15.2.2 does not contain the vulnerable code path. The CVE-2026-54265 vulnerability affects the template pipeline's resolve_sanitizers.ts (TwoWayProperty operation), which does not exist in v15.2.2. This version uses TemplateDefinitionBuilder where two-way bindings desugar to regular property bindings that receive identical sanitization as one-way bindings." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4ac248da-0507-5d84-8a65-f6ab5d824af1", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 15.2.2-tuxcare.2 of @angular/bazel. not_affected \u2014 Angular 15.2.2 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature was introduced in Angular 16.0.0 (May 2023), after this version was released (March 2023). The target codebase does not contain the transfer_cache.ts module, HttpTransferCache API, or any HTTP response caching mechanism that uses hash-based cache keys." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6b3892e4-1249-59e5-94ab-e7091daee354", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f07b8e41-bb72-5e67-9a90-2d74fcff5371", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 15.2.2-tuxcare.2 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@15.2.2-tuxcare.2" } ] }