{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:7fe1c960-5e4f-54a9-875f-b52cd68399c8",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/common",
      "purl": "pkg:npm/%40angular/common@11.2.0-tuxcare.2",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2",
      "version": "11.2.0-tuxcare.2",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:81dc439e-2e9a-546d-9ac4-4f75ba46f758",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.2 of @angular/common."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:7aae8c0e-e212-51f8-859f-29d0e89bdbbb",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.2 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:43d4a819-a44b-54a2-9c1a-9685b269e31b",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:586cbe71-0c88-5db4-89fa-a6b10df45a36",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:acfb587b-f036-5d8a-b446-c6f172b0ef54",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:a8a276db-fb1e-5f93-907f-95dbf3d78ccd",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:3439b5ee-42a0-546b-89a3-17984f018017",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:706fe205-ddc7-5542-97c2-b0c6b2229ca1",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:c354e7ac-11e9-5fbe-9b95-34bbee0283ae",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:aa34ff05-1a17-56c8-a027-19b941933191",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:9fa2d27b-c6e0-53ef-ae5d-b39137d7aad1",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:5722eaa5-bf8f-594a-adb2-8c89637319fc",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:4dbb183d-5dbb-5b64-9835-b3727d9261fb",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:9c9ac929-0299-58fa-aca1-2ce737d8b48a",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:356988f9-6ade-5296-9665-10c31c86e358",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:6659449d-2195-55e1-8158-11aca965cfbc",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:1947902f-5f79-5978-a768-546af81f1f5d",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:e609ffe5-1c1c-5171-9138-4d17da222f5c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:ed3d439f-5b00-546d-9dc0-bdfbcae7b4d0",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:5c791e96-b43d-5206-8648-89974bd4259b",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.3."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:e53b678d-c199-596b-99fa-2b6ab985b9f7",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:f455b2f2-1e32-572a-8b1b-11803e7d091e",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:f9c4f7f9-cefc-5b5b-88ee-14959c918e67",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0-tuxcare.2 of @angular/common, and is fixed in 11.2.0-tuxcare.4."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:b5f3937f-044f-567b-b540-46f971a26230",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:e1e36dc7-0c47-5406-991a-08af65946706",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0-tuxcare.2 of @angular/common."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
        }
      ],
      "bom-ref": "urn:uuid:e29cd905-d2bd-530e-9934-08a97e0b2916",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.2 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.2"
        }
      ],
      "bom-ref": "urn:uuid:4d9a690a-59d0-5186-8fea-035097d88ebd",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0-tuxcare.2 of @angular/common."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.2"
    }
  ]
}