{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:73d63a0c-59a4-543e-b7d2-3a9f30e47619",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/bazel",
      "purl": "pkg:npm/%40angular/bazel@11.2.0",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/bazel@11.2.0",
      "version": "11.2.0",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:b1d68679-4658-53c8-b0aa-98608e1c2ed6",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-66035 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.1."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:1371629d-0563-537c-8e28-62b057606adb",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-66412 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.2."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:663e1b42-517f-5eca-bc5a-701928f47821",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:d5c00822-4f13-52ab-b684-75f852bb2d21",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:ead7048f-56f6-5838-a4e3-4ac44b715198",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:241becba-e0a2-5b6f-b3a4-09b2f0ef6a3f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:42d59722-8272-5c62-8285-9b4cd47db066",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:9f4fd79d-b136-5126-81e4-5c9d2248908c",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:0f901dae-5362-51a8-8f83-c4e3649307ca",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:d7c3a287-0d16-5a1f-bcfb-6c556e5efddf",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:f9e717f2-d5e8-57cc-b5dd-fb8c20ea4a5e",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:0a434b9c-3519-5f7e-ba98-64afcb0569b0",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:a0ba7242-e448-59df-b485-ea6b0b9e028f",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:7fdf38cb-b0c0-50f5-b053-ba2cf8fe37ba",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:17af5d43-0ab0-5d42-8e72-daa7789dbfd2",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:2b78e6a3-4aa2-5bdd-a711-9c989a47db7b",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:181c5c6c-e9db-55f5-baf0-d47efbca31bb",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:fa4d0381-8652-5691-b174-d2a00f92e1e0",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:904ff90f-98de-5899-9c7d-df0252edb0f8",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:81360bdf-9eac-5736-9199-5e31d1ba3ce5",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:ac0f0a07-0df8-5405-a759-17d4120c0a4c",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:d135be64-50b8-529d-97c0-0e87b8c587ba",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:58743582-3a00-541d-8d48-d693c70321f0",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:2901e2bc-4fc3-5d86-8b7d-4e5098ce1d38",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:85ff0ca1-9bb7-588d-a100-222205e1cc83",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:91a6ca6e-cf1e-501d-84d6-6b3d0fbb6dcd",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.6."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:bb3485ea-2f58-5783-b4b5-6622221be419",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.6."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:b393f94f-e942-5925-b760-e3fa745424fd",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0 of @angular/bazel. 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/bazel@11.2.0"
        }
      ],
      "bom-ref": "urn:uuid:f78a6140-f0fe-5359-b0d5-3241b0bbc2c0",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0 of @angular/bazel, and is fixed in 11.2.0-tuxcare.6."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/bazel@11.2.0"
    }
  ]
}