{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:54a96188-c02b-589c-b41c-578a31bfb967",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/compiler",
      "purl": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6",
      "version": "11.2.0-tuxcare.6",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:5d4bfa4f-3adf-5803-8eee-4a3a8f4d36ff",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:742607e7-8c12-5a3f-beba-305b77cd39f4",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:4dfbcc66-c0c1-580f-8661-9929f56be388",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:9d465ab4-3923-551c-bd65-26e8cc6e5834",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:cb5e9d37-fa0c-5f91-9ae6-3745156ea9b4",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:53f3708b-e387-518b-b73b-1dbe5a5efb0a",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ea8f0b4f-337f-57b5-9f2a-6e5e1a754224",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ebbad441-a4d3-51e0-862e-197de7ca3f3a",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:6e76da04-e7c1-5088-9ecf-a5d583ae0e91",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ae3d8055-d65d-581c-8bd7-0ca6e36f70aa",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:b9aec68e-6a8a-50f6-8c83-e7aa58b48f29",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1c2d9f89-63cc-5838-b060-9fc250c8b9b8",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:df988f10-eb6f-548c-8361-026d432715da",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1e04bd20-19b4-5219-952e-84ed0d74d432",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:cf37e25f-83d1-59a5-9401-ed67368b04fa",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:6cd5407a-1862-58fe-9499-530274fc2255",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:eec6f45f-2189-528c-8d44-2a1d87ee7dd0",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:9088e3df-79e1-5733-bafe-0951d01c500f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:7189b7f7-71af-5811-91bd-bd30a51b8d85",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:17d34ec6-8d0e-576c-bd87-dcacfa281d21",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:b0901fa3-e0bb-5d3e-b2e5-f0a38ac86a28",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f86100af-289e-50c6-9c58-35616b7db389",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ce692a12-b7a5-5b7e-b6d7-db79e1fb3b0e",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:8cb08279-9155-5827-b625-34c27e4b57b0",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:406dfb73-b142-543b-95d4-6564825a553f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:4901df24-15ed-550a-8b29-9cba7763a4a8",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:74da7ace-4bab-5b8b-881f-04ca20c4a6bc",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:b4909b4f-01c2-5af1-9dc2-251e1628db63",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.6 of @angular/compiler. 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/compiler@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:606c94aa-3dee-5aff-ab99-1054225e9cfb",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.6 of @angular/compiler."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.6"
    }
  ]
}