{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:15dc8aaa-ef63-5946-bb03-af01c501ada9", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13", "type": "library", "name": "@angular/service-worker", "version": "9.1.13-tuxcare.13", "purl": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:672e2311-0f83-572b-a3aa-c5a5914d7d9d", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:cb49fdf9-da6c-548a-b97b-3a4bb05de9e8", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:1a512c03-cbcd-5238-b2cc-462be27723d5", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:4f1547cd-8d05-57cc-82da-88b3657ceafe", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:efa4c5cd-44de-5bcf-8ead-c808cb106027", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:0f3668e0-7894-5ad5-a8ae-e02c0cb5b05b", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:5854ec78-1546-51bc-85da-03371e181c7c", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:45e2f61e-73f4-582e-98f0-941e5cd01c35", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:cfba6ed2-146c-516c-87d8-754d12828125", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:20dfbf31-2770-5814-a1af-48824d83b78a", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 9.1.13-tuxcare.13 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.13" } ] }, { "bom-ref": "urn:uuid:2b531c3f-b0ea-5ab2-ba38-072cc6e92044", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:66ab8263-f867-5110-bee7-c8d17fb37520", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:f96cbc20-9c55-5a61-8b20-76d02019d3d8", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:d283ce0f-fdb2-53b1-b190-2a3119ba5805", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:58013acb-bc57-5223-947d-31131eac573b", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:c085b4b6-7fab-5a06-9f7b-9fa189c697d9", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:230c2108-adcd-53c1-9c6d-9f0218940e15", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 9.1.13-tuxcare.13 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.13" } ] }, { "bom-ref": "urn:uuid:2d1f0256-41e3-50cc-b679-d536dc423e4c", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 9.1.13-tuxcare.13 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.13" } ] }, { "bom-ref": "urn:uuid:a3db1e3a-b8c1-5b52-b596-2f5cbf49b6a3", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 9.1.13-tuxcare.13 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.13" } ] }, { "bom-ref": "urn:uuid:10548b0c-a230-5bd1-bd8d-70a08a032ba8", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:9417bef6-e55b-53f7-8e6d-f7e7a7870a6b", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:a296b819-34f8-5710-994e-d7267d2d9e3a", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 9.1.13-tuxcare.13 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.13" } ] }, { "bom-ref": "urn:uuid:86baab95-7689-59b5-ac74-a9adfb9f3a8b", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }, { "bom-ref": "urn:uuid:3bc7ce15-e4db-5e7b-ae51-9cdfc954873f", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 9.1.13-tuxcare.13 of @angular/service-worker." }, "affects": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/service-worker@9.1.13-tuxcare.13" } ] }