{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:f79938c4-4568-5115-b2e2-ff3d0a26a3f8", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4", "type": "library", "name": "@angular/bazel", "version": "13.3.0-tuxcare.4", "purl": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:5ead2c79-1eb1-5497-b976-34e82570319a", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:278a62a3-c4e2-5fbd-83f3-b9474bcb6ec9", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ffd72ff9-89fd-524e-b2ab-6fe7622faeca", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c60c4eca-6819-566b-8f30-0ff136be585d", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d24a6f1a-8da8-5fc0-ab7b-151994755fa1", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 13.3.0-tuxcare.4 of @angular/bazel. not_affected \u2014 The target repository (Angular 13.3.0-tuxcare.1) is NOT AFFECTED by CVE-2026-41423. While the target lacks the explicit sanitization that the upstream patch adds, it uses a fundamentally different URL parsing mechanism (Node's url.parse() without base URL) that does not extract hostnames from protocol-relative URLs. The architectural difference prevents the SSRF attack vector from succeeding." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dba114bb-c483-5fb7-bf42-95da7c39b880", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:42c4a9f0-07d5-5d63-b552-85385b103631", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1b7725a0-8eab-5c6e-9eb8-b735d5a19b6e", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cf556e37-fa45-597f-8f0a-492348ac7c7a", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 13.3.0-tuxcare.4 of @angular/bazel. not_affected \u2014 Angular v13.3.0 is not affected by CVE-2026-50170. The vulnerable component (HttpTransferCache) does not exist in this version. The HttpTransferCache feature and automatic HTTP response caching during SSR were introduced in Angular v16+, while this target is v13.3.0-tuxcare.1." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:488615be-57a6-5e27-b5c1-864f5e6db62e", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6ee77fad-6948-5366-985f-fb673b78c3fb", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:681196e6-9b8b-53b8-bedc-889f1c2904fc", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1f0cca3b-c396-5df8-92c7-fc7535d5569e", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:65d54c99-b9dc-5139-89cf-11f7b54cfbe1", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d8bbfc1a-a482-5307-b782-a4eecc1690fa", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fbdf117b-137f-51a5-9d50-195587aa67d0", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 13.3.0-tuxcare.4 of @angular/bazel. not_affected \u2014 Angular 13.3.0 is not affected by CVE-2026-54264. The vulnerable method newRequestWithMetadata() does not exist in this version. The AssetGroup class creates new requests with only URLs when fetching assets, never preserving headers. On cross-origin redirects, the code creates a completely new request with no headers, preventing sensitive credential leakage." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2502426f-f04d-5e1e-af49-15cd5443c814", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 13.3.0-tuxcare.4 of @angular/bazel. not_affected \u2014 Angular 13.3.0 is not affected by CVE-2026-54265. The vulnerability is specific to Angular's template/pipeline architecture (introduced in v14+) where TwoWayProperty operations bypass sanitizer resolution. Angular 13.3.0 uses an earlier Ivy architecture without the template/pipeline system, where two-way bindings desugar through the same parsePropertyBinding() function as one-way bindings, rece..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:43488457-f665-5269-a409-03f0a27194b7", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 13.3.0-tuxcare.4 of @angular/bazel. not_affected \u2014 Angular 13.3.0 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature with weak DJB2 hash-based cache key generation does not exist in this version. HttpTransferCache was introduced in Angular v16+, and version 13.3.0 predates this feature." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7e62d2b4-465c-5840-8b16-0dfa065818d0", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b7c328c0-0567-516b-a55b-f0071271a57e", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:277deb52-ca7d-53a1-b5f9-621440f0bb0a", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 13.3.0-tuxcare.4 of @angular/bazel. not_affected \u2014 Angular v13.3.0 is NOT AFFECTED by CVE-2026-68945. The vulnerable HttpTransferCache feature does not exist in this version\u2014it was introduced in Angular v16.0.0. The cache-key collision vulnerability requires the HttpTransferCache's sortAndConcatParams() function in transfer_cache.ts, which is absent from v13. Verified by filesystem inspection, git history, and existing patch documentation (CVE-..." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:885dd316-261f-5905-bac0-b13653dade1a", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:385d413a-66ba-5459-bc73-18deadce1de6", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 13.3.0-tuxcare.4 of @angular/bazel." }, "affects": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@13.3.0-tuxcare.4" } ] }