{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:3bbc2d1f-85c4-55eb-96fb-03150e31942d",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/core",
      "purl": "pkg:npm/%40angular/core@11.2.0",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/core@11.2.0",
      "version": "11.2.0",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:fe421cb1-a350-579c-ad52-bf2added9e8e",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-66035 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.1."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:188cc175-5edf-52ef-b826-3454690783a5",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-66412 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.2."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:50dc8cab-128f-500b-b2ab-ab9f511f7fe2",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0 of @angular/core."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:41f236eb-df13-597a-8f39-33c121e6a3bf",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:22b10229-459c-5aee-a736-e2d0ff977f0c",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:513d38a6-b729-5da5-8fa4-88ea5bcd94de",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:3cd8a1cd-11d9-5681-84b9-794c0586b36d",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:07d796c2-f964-5a62-9481-a1cc8d73eb32",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:eda8b8ef-a078-51fd-91aa-c4356bf4c05f",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:e7996ba6-99a7-5385-9050-33d9a548e0ab",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:74fcc26f-6353-5abb-9a4b-40966790517a",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:b0d48c02-307d-5650-a314-0b1d32d05504",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:5777ab09-1270-5a3c-83b9-f70668d742e1",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:09d1afcc-fce7-524e-9907-76da12278893",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:a2c75282-7fac-573e-85ab-ac063f8b5936",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:041375e0-2d4a-51c2-9e33-9832a558a162",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:794decb4-2506-5668-96e7-50146fd11cd1",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:62732052-64af-50dc-a50e-97d0faadc0cd",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:ecd68e0e-b06b-5745-841a-0b081f9986c1",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:1ae1a952-0da1-5a53-a6b0-0d6654c50313",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:835ef42e-384c-5663-98f4-c69d457e6572",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:361679f6-5dec-54a9-9e5d-2ff78ee6bf1c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:4c605776-0e64-5226-8800-a5f1e5ccbcbb",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:38ab9ddf-faed-5f65-aa6a-9a0e928b4c23",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:9b883261-7965-50b9-a15f-33e74897e012",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:46d9527a-bc94-56d9-b78e-f01cf8f37a85",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.6."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:3e168866-5ba4-5a9a-859e-15aa0ffe157e",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.6."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:8e75d72c-c5c0-5196-a022-cf8139d3c54c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0 of @angular/core. 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/core@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:7b8a10ad-006d-5a61-87d6-8749d6432b33",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0 of @angular/core, and is fixed in 11.2.0-tuxcare.6."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/core@11.2.0"
    }
  ]
}