{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:44f0d05d-6efa-5e59-ad2c-5b4bd6d82405",
  "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.3",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3",
      "version": "11.2.0-tuxcare.3",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:65a616f4-07f8-5b56-b3a3-3ad0fcad4d45",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:4b6b56e0-ef38-5a81-a25c-cfba007e81f4",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:a70dec64-7791-55dc-bb36-bdc70dbf0e16",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:c803e024-5cb0-552f-bd49-8f5bd7682c58",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:651c61c8-c4fc-5735-8d90-7908e007fd56",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:079af06c-58b8-5681-9bb8-cb6e16cc9dac",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:54ef4e8f-0ddd-59a1-a96b-21e327d304c5",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:be4ee796-4513-5dd2-953d-00d4c4be4d2e",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:a5aa67f7-20dc-538b-b527-125502d9c4db",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:cc02c9ca-ca93-544c-abe9-3fc1c5b2a138",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:76031aac-235a-58a4-ae57-84535a10cb1b",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:3042b202-ef98-5daa-b296-d265369c778f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:882b19b6-cb42-573f-a6b2-1fc4e553e7ac",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:c62a5b95-8905-5f4b-a97a-4490071f4911",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:41733e54-7dad-5c0d-b779-0e0f74214aaa",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:eb6936b8-2da9-5758-92ee-f12dd3c34a1c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:eb5ed225-4667-5514-9ae1-5ab4abf74e27",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:24b76317-9568-5884-9ccf-4fca0e04e400",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:f4a45e4a-9a47-5dcb-826c-268efccb7f27",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:521179c5-3923-5b87-bdc7-93c0ee9afd6d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:e9b55dd4-f3da-515c-8168-c75a001cc464",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:6d29befb-e6d1-5943-900d-db7a90cf5e09",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0-tuxcare.3 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-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:1cb83b68-b45c-5a6c-8889-7785acc5fc6e",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0-tuxcare.3 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-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:2473ffa5-14f5-5c01-a720-3843dfd5d9df",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:d903b52e-fc68-5c7b-ad64-a73097cbd3c7",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
        }
      ],
      "bom-ref": "urn:uuid:e738c411-d809-50f0-a86d-bb1dc66385cc",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.3 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.3"
        }
      ],
      "bom-ref": "urn:uuid:d7969543-087a-537f-9a23-07d5cdb3eb95",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0-tuxcare.3 of @angular/service-worker."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/service-worker@11.2.0-tuxcare.3"
    }
  ]
}