{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:b973720d-72cb-5838-84b6-45981b32c81e", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12", "type": "library", "name": "@angular/upgrade", "version": "9.1.13-tuxcare.12", "purl": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:6c62f982-a44e-5724-8545-4e1a9197f9cd", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:6a142b9b-e7af-5484-ae8d-9b9f2d7e03dc", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:776c3cd5-8798-588a-b87c-d2d4dfab8515", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:8b6d03ff-0ff3-5b18-903a-d4972f90507c", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:5b687ce8-5ab8-5509-97d4-c47935c5ed8c", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:2737e343-3fa3-5af1-8c3e-aeb052e0c252", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c8dc4a1d-5cf8-5976-b759-5fb9b822170e", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:32f06ad8-1a42-598a-8c13-6614b9032769", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:ad014216-2048-50fb-865b-9d96b78a8f74", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c01257e4-5202-52f9-b3ff-690de6000715", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 9.1.13-tuxcare.12 of @angular/upgrade. not_affected \u2014 Angular v9.1.13 is not affected by CVE-2026-50170. The vulnerability exists in Angular's HttpTransferCache feature, which was introduced in Angular v16+. This feature does not exist in v9.1.13, making the vulnerability pattern impossible to manifest." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c48f1dd4-55d2-5f69-a09e-9bcccaf9b5ae", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:4d9857a0-14ef-5b99-b2e9-c9dc3b4851bc", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:f71a58d1-d5e2-5974-8eeb-d2539b030ab5", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c273dfd4-158d-5017-94a9-a82537a2a5e5", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:676d981d-5756-5624-83af-36ec1bbf3689", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c9bdde98-6eb3-58e9-8627-d90bf7ef437b", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:f8098018-2711-5bdc-aa3a-6b68090af7d3", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 9.1.13-tuxcare.12 of @angular/upgrade. not_affected \u2014 Angular 9.1.13 is not affected by CVE-2026-54264. The target repository uses a fundamentally different request reconstruction architecture than the vulnerable upstream versions (22.0+). The vulnerability requires the presence of header-copying logic during request reconstruction, which does not exist in this version." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:d9de510f-d251-5a99-9533-bfbfa56de1d8", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 9.1.13-tuxcare.12 of @angular/upgrade. not_affected \u2014 Angular 9.1.13-tuxcare.9 is NOT AFFECTED by CVE-2026-54265. The vulnerability exists in newer Ivy compiler's template/pipeline architecture where TwoWayProperty operations bypass sanitizer resolution. This version uses View Engine and early render3 (Ivy) implementations where two-way bindings desugar through the same parsePropertyBinding() path as one-way bindings, ensuring identical sanitizer ..." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:2435ac6c-4ad9-56d9-8e4c-3912959064e1", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 9.1.13-tuxcare.12 of @angular/upgrade. not_affected \u2014 Angular 9.1.13-tuxcare.9 does not contain the HttpTransferCache feature. The vulnerability CVE-2026-54266 affects the hash generation in HttpTransferCache, a feature introduced in Angular v16+. The target version (9.1.13) predates this feature by many major versions. While TransferState (generic state serialization) exists in v9, there is no HTTP caching integration that uses it. The packages/c..." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:d10784c2-1f8e-5186-93df-e68ca3e05aa1", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:ff5c22fa-af7b-589d-8a4a-379f01176521", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:03ce2915-5fb6-5499-8f8a-23f550ce2ace", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 9.1.13-tuxcare.12 of @angular/upgrade. not_affected \u2014 Angular v9.1.13 is not affected by CVE-2026-68945. The vulnerable HttpTransferCache feature was introduced in Angular v16.0.0 (March 2023), approximately 7 major versions after v9.1.13. The target version does not contain the HttpTransferCache code, the transfer_cache.ts file, or any automatic HTTP request caching mechanism that could exhibit the cache-key ambiguity vulnerability. While v9 does..." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:67ce564d-2de2-578c-89f7-f71f759cf142", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:891cdf04-7c19-5e45-ba1f-c82e0c2cdadd", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 9.1.13-tuxcare.12 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@9.1.13-tuxcare.12" } ] }