{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:89318429-361b-5ae1-b9ef-3519a74fcad0", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3", "type": "library", "name": "@angular/upgrade", "version": "15.2.2-tuxcare.3", "purl": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:d828def2-d95b-5315-8750-b6bf67bed6a5", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1268d4b9-62c6-5a1d-99b2-31184c1bcb28", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d48c8e77-4811-5c01-8e5d-5c4fb63b3608", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:afb3c725-f7b3-52ee-ac43-f5396007cb22", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1e6f0b82-320b-51c3-967b-cfa23eea3ff4", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 15.2.2-tuxcare.3 of @angular/upgrade. 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/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1b527d26-05e7-5050-a1e4-3e8b8643bc64", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f6131251-bbfc-5219-9bb1-f060e765369f", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a58b7eab-eabe-5fda-9fe5-1222e6a28c2f", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0ac9db7f-a724-5b54-a76e-42a4320066e4", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 15.2.2-tuxcare.3 of @angular/upgrade. 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/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:085d9e1d-a1f0-55e6-a555-e391deaf934b", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:33fdbe4c-3edf-5495-a24d-f1aa6b5bf323", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5f2772c4-0252-54c9-b92b-9e622c80b8c1", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ad2e450f-335f-55eb-b7eb-97b5c1cecd5b", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:02d8b40e-5815-5925-94ad-16ce411fb889", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:00153821-0657-50d0-9055-bd61d51281d9", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f35cfc1e-a386-5784-83cb-5ae6c575e7c7", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c8ac9565-d41d-595c-bf84-0973c2583496", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 15.2.2-tuxcare.3 of @angular/upgrade. 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/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5d54dc4e-7cfa-57a2-ad84-34c38c3176e2", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 15.2.2-tuxcare.3 of @angular/upgrade. 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/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7d1e4b43-5307-5363-a648-9608ff462d4a", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:137c201a-fd82-5c6f-9412-d4aebfdc155e", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ddd61eff-cf89-5f1f-840f-8a27562d5590", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 15.2.2-tuxcare.3 of @angular/upgrade. not_affected \u2014 Angular 15.2.2-tuxcare.2 is not affected by CVE-2026-68945. The vulnerable HttpTransferCache feature does not exist in this version\u2014it was introduced in Angular 16.0.0, after the target's release. Without HttpTransferCache, the cache-key collision vulnerability described in the CVE (where repeated HTTP parameters like `role=user&role=admin` collide with scalar-comma parameters like `role=user,a..." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6518cc3d-8261-597b-b4aa-a5fc032a20ca", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0f007c6d-3f37-519f-aa35-bcedd675786e", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 15.2.2-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.2-tuxcare.3" } ] }