{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:459d8d3f-2291-5dc7-8f16-03749fc9d70e", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12", "type": "library", "name": "@angular/service-worker", "version": "9.1.13-tuxcare.12", "purl": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:39fd77bc-a0af-52a1-8a57-0627454b1c10", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:239aa3e4-30a7-5cf8-b603-dbea6028ea4e", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:1a10fb9b-0289-580c-8f4e-4647dfc5f181", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c9a5a339-5f7d-58ea-902e-3bfa7de06a41", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:60b963e1-ad7e-59b1-8b50-3867afb41618", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:0867fb59-9c6d-5877-a3cc-d6c141a9bd81", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:c473e929-2e6d-5a84-bbc6-d12725521777", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:7e2c3c8a-3080-5da1-a715-dfb00711eef1", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:b37642a2-12f9-5517-8556-595527a91a59", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:1f098edb-081e-522d-a104-0f80ef5d3fe8", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 9.1.13-tuxcare.12 of @angular/service-worker. 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/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:fb378af6-f781-50c9-ae1e-45feb36d07e1", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:1c5d6e75-9679-5cbb-9b0f-13390c80191e", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:5e9fcd2c-a0be-5309-a8a2-a5047abdc2b1", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:850f710b-5f86-5989-8759-376f3f13bf20", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:cb3ceda0-264e-5475-8ccf-867ce76a93b9", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:a870a15f-04cb-54c8-8c7b-e4bd2763f166", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:4c477cdf-7317-57ea-b0fe-85599e79af8d", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 9.1.13-tuxcare.12 of @angular/service-worker. 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/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:4addaf54-bf70-5b78-a92a-bf48c6136816", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 9.1.13-tuxcare.12 of @angular/service-worker. 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/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:e0a92c2f-0942-58cf-b65f-f479971d0745", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 9.1.13-tuxcare.12 of @angular/service-worker. 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/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:0163f1c5-55fe-5609-9ff8-23f161d7dfde", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:30b204c0-b0c2-5b41-ba1e-4238f6579774", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:0e7960cb-2c11-5366-b65b-0b762a7585b5", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 9.1.13-tuxcare.12 of @angular/service-worker. 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/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:860175ef-f252-536b-b90f-5aeaeaa3d96d", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }, { "bom-ref": "urn:uuid:221ad153-4ab5-52c3-9119-49b883df435d", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 9.1.13-tuxcare.12 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.12" } ] }