{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:a0090c08-936b-5720-8bb9-833371693caa",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/bazel",
      "purl": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/bazel@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/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1750c4d0-0392-5937-9bde-3a3116e599ef",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:931ff8eb-2976-5467-af8a-d8b37163d5e2",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:8aaa651f-b026-5b62-a6c0-2a14345b28c7",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:8f0251ab-1d47-59de-bad3-3f871e9bc18b",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:d2a494ac-a045-5789-840e-8de5565ded61",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:d777d5cb-b763-5b58-a366-4c04b7e9f065",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:956398f5-9619-5616-882d-b60d6f22636f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:44d2c731-6097-5a43-85e8-409d656b954d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:765fcd44-77d8-5b4d-adef-07421583145b",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2a042a1e-60ac-54bb-a40d-87a195d09193",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:7b962ac7-53c2-5990-b099-5aa69f24ec96",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f56407a6-6fd7-5a02-a13b-1c239b33a4d8",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:63b69d85-a44c-56d2-ba4e-7c34d61c6c06",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:555a95da-b133-5ac3-a31e-cb373910f2cd",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:60e19279-80fd-54fd-bbb6-3098401570cc",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:850a01f6-cff6-5989-8fc6-f823cb11c5c4",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2a98998d-96f8-5b73-be78-45112932fc5e",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:6ec6bd20-45a1-5638-803d-9b12d9f50829",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1072c24d-0482-57b5-9d7f-4207b5e90756",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:c227e8a3-b513-59bb-9f84-98ac0469981f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:0c44b6ba-fcb2-54b8-9082-487bac25001a",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1d0fdc2c-190b-5a37-9854-c1e2a97c3fe4",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:cb383bdc-8cb2-5012-8afb-8660aa2cda7f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2ee33418-6283-50e0-885b-5894154e36f6",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:a97f3831-0abe-571c-8cbf-33faa79db931",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:93f94e37-ee4d-58a1-b109-96c60a64181d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:399989f9-f24e-5490-ab24-beef761058f7",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:80fcbc19-f0f4-545e-92a4-c3b86e6f27e7",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:272461eb-9407-5f6b-8026-c317232f3421",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.6 of @angular/bazel."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.6"
    }
  ]
}