{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:eaca32fa-a843-5866-9a9d-a7c41bb6581c", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/service-worker", "purl": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7", "type": "library", "bom-ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7", "version": "11.2.0-tuxcare.7", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:5ca96e76-60c0-5610-b231-533d29edeb9f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:9292b414-dfe0-5330-91e8-b8f310ee11c5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:fd2398b4-2677-5f84-9a4f-565ca3b0cb25", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:31960ab5-2151-5543-9464-42e9110d4624", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:a420d234-314e-5a56-b3a7-3cfc6e53f71e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:355a1c44-a973-564b-af55-26aa3baa519e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:3525ea5d-25ed-57ac-baf9-a7a7e6f964a4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Target version 11.2.0 uses Node.js url.parse() API which does not perform hostname hijacking with protocol-relative URLs. The SSRF vulnerability (CVE-2026-41423) specifically affects versions using WHATWG URL constructor without the defense. The target's url.parse() produces empty hostname for inputs like '//evil.com', preventing the SSRF exploitation that requires hostname replacement.", "justification": "code_not_present" } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:5904882d-5820-54c6-89fa-ce01bbf6cced", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:9d583bab-d39f-5afe-a9e8-f685761a1f5f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:685506be-907e-58d0-8a30-483da3268bd6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:cee899c0-3003-5f7e-ae58-ecbfa5bb503c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-50170. The vulnerability exists in Angular's HTTP transfer cache feature, which automatically caches HTTP responses during server-side rendering (SSR) and reuses them during client hydration. This feature was introduced in Angular v16+ and does not exist in Angular 11.2.0. The target repository lacks the vulnerable code path entirely: no transfer_cache...", "justification": "code_not_present" } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:c8de6080-1d7c-5e09-82f3-341ed9aa953b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:5c28b3fb-81ad-511c-9eb4-d447e669b975", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:ffc64b7d-ea29-5aa0-81bd-8f3a0c5d5034", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:da1f4941-5adc-5f60-99be-376ae73e2099", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:e01f2c49-80c9-5438-b2b2-c9632edd5cb8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:d6bdeefe-7f59-5e20-b90a-790981c00daa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:8105631c-81ec-521c-8d06-a770a2ab9a97", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Version 11.2.0-tuxcare.2 is NOT affected by CVE-2026-54264. This version lacks the vulnerable code pattern - asset-group requests are reconstructed using URL-only (no headers forwarded), and data-group requests use browser's native fetch which strips sensitive headers per Fetch specification. The vulnerability requires a header-copying mechanism that does not exist in this version.", "justification": "code_not_present" } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:f0fadf22-7ff0-5edc-98c0-5e28155fe91a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Angular v11.2.0-tuxcare.2 is NOT affected by CVE-2026-54265. The vulnerability requires the Ivy template compiler pipeline's TwoWayProperty IR operation introduced in later versions (v20+). This version uses an earlier compiler architecture (View Engine + early Ivy) where two-way property bindings are desugared through the same parsePropertyBinding() path as one-way bindings, applying schema-de...", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:a990614f-517d-5647-8349-475650a8c536", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Angular v11.2.0 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature (introduced in Angular v16+) does not exist in this version. The transfer_cache.ts file and all related APIs (HttpTransferCache, generateHash, makeCacheKey, withHttpTransferCache) are completely absent from the codebase.", "justification": "code_not_present" } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:d9d008dc-b41d-5e1e-a88d-46cb66cf6fc8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:55b361f7-9be8-59c7-983b-489e0a940eff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:a7dfe41d-91ba-5311-9cc6-773764ec730f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-68945. The vulnerability exists in HttpTransferCache, a feature for automatically caching HTTP requests during Server-Side Rendering (SSR). This feature does not exist in Angular 11.2.0. HttpTransferCache was introduced in Angular v16+ as part of the modernized SSR architecture. The target version predates this feature by multiple major releases. Only ...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:8bfa127c-315c-5a2d-94f5-2913b249dd1e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:2712547f-5d07-5829-bdad-07714f98ff19", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:31c79815-638c-5681-ad9c-369ed4c00ac5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-88056. The vulnerability requires a `String.prototype.trim()` call in URL resolution utilities (`parseUrl`/`resolveUrl`) that creates a discrepancy with WHATWG URL parsing, enabling SSRF attacks via Unicode whitespace. This vulnerable code pattern was introduced in Angular versions post-11.2.0 (appearing in 18.x-22.x) and subsequently fixed. Angular 11...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:c49238eb-da8e-55ac-a3f6-597dbea0b134", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:14a12138-2fce-50cd-974a-ba2125094dcd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:88243acf-0133-51a8-8f43-bb77b0b38f2c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.7 of @angular/service-worker. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-88059. The vulnerability exists in HttpTransferCache when using hierarchical HttpClient configuration with withRequestsMadeViaParent() - features introduced in Angular 16+. Angular 11.2.0 uses the legacy Module-based HTTP API (HttpClientModule) and does not contain the HttpTransferCache component, provideClientHydration(), withRequestsMadeViaParent(), ...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:1bff4c19-acd5-5a9c-a442-e8e03d54e426", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.7 of @angular/service-worker." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.7" } ] }