{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:73e60375-e23f-5df8-9080-f19f177d0835",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/common",
      "purl": "pkg:npm/%40angular/common@11.2.0-tuxcare.6",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/common@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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:38c16edb-9b81-5f15-bad5-2b87220ea8c7",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1ce26443-7247-5fd0-aab0-0aa490eb4591",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:459bec3e-a3fe-5e0b-9fa6-a0a92672bfae",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:c058f3e9-7e80-5e04-ac17-53c64537a43c",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:fc536530-9d5a-51e5-9c5d-7bb170b9ae88",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:599beba0-196d-5128-b32e-5c7e9ab2ae32",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:73cc5590-e8de-5bae-bde6-331ffec33d2e",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:9d686db3-661c-5a78-983e-91a702e2fe41",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:46a1a0c5-95d3-5496-91d8-1fdb25cc5ba5",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:589456ca-5239-5fe1-9641-4b5c365aaf48",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:d0737d05-7bc3-593c-80df-8e9a4b255150",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:e2a52e93-608a-5891-a6b2-a785ec7671be",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:7ba29215-7e2c-5435-9f6d-3833e87edf24",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:9d6a4a4d-cf6f-54b0-b974-e219e6063ab7",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:12f80dae-0f70-53c1-bde2-ba1821bc94e1",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:137bdf67-aa5a-5a0c-8d45-923fb2cb3138",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:6bde1459-ab36-58de-8e39-3e40d9460253",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f3a0e278-822f-5ef8-beae-0de0dcc4a790",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:7c650496-1129-5a5e-95a3-7797ab3a7c07",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:48fc385b-36d5-5c50-8468-4bef0f1e2226",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:3f526472-83ee-5a5e-b699-150a12a5799f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:c46085b9-b911-53b2-b0dd-dbb6d00f1d64",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:a63e6691-140a-53e5-bcd1-5631abe5ebb5",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:3d24130f-4bac-5d2c-91c6-c81b6610d1c6",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2a35683b-ed68-5cf5-958d-6c2c760583bb",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:5be58996-98b3-539d-ad16-22b3ff957be3",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:d1bcb4e5-6468-5f91-8c80-de837d02bde8",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ef05b5ff-d474-5c17-9a5e-5c417866ab15",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.6 of @angular/common. 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/common@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:af8b3763-774b-5bf8-acdb-2f246cf25c89",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.6 of @angular/common."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.6"
    }
  ]
}