{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:0a120dac-2b6d-5aaf-8326-e0b2ec1b0717",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/platform-server",
      "purl": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/platform-server@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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:5dfe7e71-8583-5398-a2ff-ad33d1677339",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f44ef346-ea45-57b9-be67-7f8c6480b27c",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2b2a8429-96b0-52c6-9a08-38f0fdfc9386",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:fb112268-39f4-5e2a-aa69-091204d38281",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:62629f8e-ff9c-56ec-bd0b-ad243a59cf09",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:b47bbc13-9061-54d6-bbba-59e80549835f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2182f9cf-7de1-5585-aae0-26695d459a57",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:860e0b09-0d25-59db-871d-5c48922c4dd1",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:d378e41e-5ead-54f1-81d0-41d747d9e6b9",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:501fe19d-fa81-5496-86fa-ecd7fa8fb05c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:21057074-5481-5b6e-8305-7f2faa9df105",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:3feb9365-9b15-5750-9fad-6246bd98dbe6",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:203a41d6-2a76-5c0a-8e47-576fbf44f03e",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:77b84c6c-8826-593c-b159-d98d676713c7",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:bb062198-e360-556d-8a95-c9bb067e8ca0",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:33d4e235-03a2-504c-be86-62e622be889d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:e3cbf035-b575-5c5d-a3e6-945a950223e7",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:2bcb4ebe-726b-5a77-b40d-5ff5aba0759b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:a7df3cb7-edd7-5f05-befe-10554337f1ab",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:af9efc8c-e057-55ba-89fd-b44bc38bef65",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:80632228-4e28-5f31-9171-e48f82e1d4b8",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:37b29b2b-714e-51e3-98d0-9c89e3c9ff95",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:7e390018-c6a0-5042-8acb-5811eae36974",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:44db01ef-e364-5705-af57-36bfa34041c2",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:b22ae80c-d660-526f-b8f1-05ebf66aa828",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:89f4c5ef-de5a-59b7-a6be-502fb31bc59d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:43c2de19-2bbc-50d0-b119-828c265256cc",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:612d0b12-eef1-5ce2-a834-cd7a1aad7ff4",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.6 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:e8d1a908-9c17-526f-9428-82cd9cfbf221",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.6 of @angular/platform-server."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.6"
    }
  ]
}