{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:a28c4c4e-30a2-5f86-96df-1c9407bca30a",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/service-worker",
      "purl": "pkg:npm/%40angular/service-worker@11.2.0",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/service-worker@11.2.0",
      "version": "11.2.0",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:26c7f793-2b66-51e8-b0aa-06adbdb5a995",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-66035 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.1."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:00f195fc-223d-5c60-ac99-82b2bb4eaaac",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-66412 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.2."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:d88d92e3-f312-59bc-a427-442de0c60ce6",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:a752fd58-e0da-50f3-b7c7-179829091123",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:6a90b9cd-dfb9-50da-bff0-67c704882e15",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:bc3b0d1e-fbe1-506d-afd0-873918fd3640",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:db09fafc-ab46-5c03-b9fa-9230f8112e4c",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:3f2e2917-733f-5b56-9294-3f90867dad86",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:853d6ebb-f7dd-5541-8dcf-3448cc6a1f41",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:8366c225-f038-5974-bd93-64ba26ba8384",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:d7f46a6a-3cc4-5640-b3fd-14a2ea58906b",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:21a36f50-5cfc-5af7-b525-a033fa8be05c",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:94eb1084-f82e-5ac8-bd3c-0c19e116aa15",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:660188ce-6367-5e55-9845-5ec8f163b982",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:24ee924d-5741-53ee-bb8b-e735095a68a1",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:cea35eaf-da9a-5975-b0b5-44f69aa602f9",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:d8d32c11-7a28-5fa9-bf7f-2dcff9f5340e",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:36b38fc4-f1b2-5ca5-95dd-4431fbd2d315",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:87631089-0ee0-54a9-9759-c8935183440c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:79b43d03-2b10-555c-9824-acb614d2dff0",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:048618e9-a6d5-5ccd-a820-bee69f51ad9d",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:38f677c8-59cf-5c60-b815-80fb5d2d47be",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:29391c31-4d07-584d-b0d5-4d11c4490dbf",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:1083ee76-2789-51ae-950d-1da4f17dc7f5",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:88053674-c61f-5ca5-a7ee-504cf32035f4",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:3966c00e-e098-5f3a-b0cf-1ee2bb7fa530",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.6."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:7d4781dd-f5a0-5792-958b-ca780f37ec2d",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.6."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:6f4071dd-8c9d-5880-acc3-81ee3a026aac",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0 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"
        }
      ],
      "bom-ref": "urn:uuid:3e369c8b-ad3c-5bb4-93ae-4d041a4f3db2",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0 of @angular/service-worker, and is fixed in 11.2.0-tuxcare.6."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/service-worker@11.2.0"
    }
  ]
}