{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:6ba2899d-1bdb-510c-8ccf-4019895dd406",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "@angular/upgrade",
      "purl": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6",
      "type": "library",
      "bom-ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6",
      "version": "11.2.11-tuxcare.6",
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2025-66035",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ff92de71-6635-51a2-a306-42a24e68bdb5",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2025-66412",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:defea558-70c3-51ef-95a9-89503132530a",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-101895",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:bec5d767-b66e-5c18-9cac-55458ff9ed0b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-101895 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 The vulnerability exists in domino's HTMLParser.js (the HTML parsing library), not in Angular's own source code. Domino is declared as a dependency (domino ^2.1.2) in packages/platform-server/package.json but is NOT vendored in this repository. The vulnerable code path (after_doctype_name_state infinite loop) is not present in the Angular source tree at SHA 5c9a2f029106d75c83ecdedae9f1070dbbedd...",
        "justification": "requires_dependency"
      }
    },
    {
      "id": "CVE-2026-22610",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:9e776511-930f-56fa-9b7a-6bc9c2db16da",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-27970",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ee39d14a-388c-58be-8f6f-4b0bae46f8c7",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-41423",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:4dcd4a24-2122-564a-9f58-a8ef3655a65f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-41423 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-46417",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:182854dc-14f2-577e-80ab-77a27ed6e367",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-50168",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:a5c6b77c-261c-541d-912f-4f0dc229d677",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-50169",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:44a243be-5e5d-5743-b551-250a7d31978b",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-50170",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f10b6a2c-20be-59ef-bd23-84415b6dbb72",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular v11.2.11 is NOT AFFECTED by CVE-2026-50170. The vulnerability affects the HTTP transfer cache feature introduced in Angular v16+, which automatically caches HTTP responses during SSR and replays them during client hydration. This feature does not exist in v11.2.11. The target lacks the entire transfer_cache.ts module, withHttpTransferCache API, transferCacheInterceptorFn, and client hyd...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-50171",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:e9502fef-df98-5478-8988-ccd9cb118259",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-50184",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ccef40c4-f0f2-5a85-88fe-e41df2708c67",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-50555",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:921b6bdc-dc80-575e-b817-974dfcf8f892",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-50555 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. already_fixed \u2014 CVE-2026-50555 has already been fixed in the target repository. The fix is implemented in tools/postinstall-patches.js (lines 96-139) which patches the domino dependency during installation. The fix adds NOSCRIPT to hasRawContent, removes _scripting_enabled conditionals, and implements escapeMatchingClosingTag to prevent XSS via raw-text element breakout.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-50556",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:1af0081b-43d0-5c62-b175-38552a92e881",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-50557",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:7b353875-2306-5d6a-82d5-52f23cc34425",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-52725",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:9d406b4b-e88c-52f2-a8a4-c256bba18ae0",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-54264",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:b07a4d32-9a76-5fb6-9e7a-7c7671849b84",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular 11.2.11-tuxcare.2 is NOT AFFECTED by CVE-2026-54264. The service worker in this version does not forward request headers during asset reconstruction, eliminating the cross-origin credential leak vulnerability. The vulnerable method `newRequestWithMetadata` that copies headers from the original request does not exist in this version.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-54265",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:55376fef-cbff-50f4-98b9-c9adedfcc6a1",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular 11.2.11 is not affected by CVE-2026-54265. The vulnerability targets the new Ivy compiler's TwoWayProperty operation in the template compilation pipeline, which does not exist in Angular 11.2.11. In this version, two-way bindings desugar through the same sanitization-aware parsePropertyBinding code path as one-way bindings, ensuring security-sensitive properties are properly sanitized.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-54266",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:08c5d5d3-95ba-5f81-85ae-cc4b29388937",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular version 11.2.11 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature with weak DJB2 hash-based cache key generation does not exist in this version. This feature was introduced in Angular v16, and version 11.2.11 predates it entirely.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-54267",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:446a6f69-c366-5d17-86a1-b96b9a414d8f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-54268",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f019e974-df7e-5b6c-8f20-797ddfe4de0e",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-68945",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:ac883d71-c54c-5d49-a7f8-ad297759ac50",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular 11.2.11 does not have the HttpTransferCache feature. The vulnerability CVE-2026-68945 affects HttpTransferCache, which was introduced in Angular 16.0.0 (March 2023), approximately 2 years after Angular 11.2.11 was released. The file packages/common/http/src/transfer_cache.ts does not exist in the target version. Angular 11 has a generic TransferState feature for manual state transfer bu...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-69149",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:96dd3c51-e11d-543a-ae52-ed528ed91eaf",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-69151",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:42cdaa5b-b124-5132-8721-ddede2719a30",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-88056",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f66207df-fbb6-57ec-a81f-b4a56231035b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular 11.2.11 is not affected by CVE-2026-88056. The vulnerability was introduced in Angular 19.x when URL resolution logic was refactored to include `String.prototype.trim()`, which strips Unicode whitespace and creates a discrepancy with WHATWG URL parsing. Angular 11.x never contained this vulnerable code pattern\u2014its URL resolution directly uses WHATWG URL standard without intermediate str...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-88057",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:af10fb83-40c1-517c-a85a-205170e49f27",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-88058",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:6adb6ad3-3499-52dc-8e8b-ca845b3ecfdb",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    },
    {
      "id": "CVE-2026-88059",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:04a1475e-7f57-540d-9c50-e334bcc118a8",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.11-tuxcare.6 of @angular/upgrade. not_affected \u2014 Angular 11.2.11 is not affected by CVE-2026-88059. The vulnerability requires HttpTransferCache interceptor and the hierarchical HttpClient delegation API (withRequestsMadeViaParent()), both introduced in Angular 16+. Angular 11 lacks the entire feature: packages/common/http/src/transfer_cache.ts does not exist, no HttpTransferCache class or interceptor is present, and neither withRequestsMadeV...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-88060",
      "affects": [
        {
          "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
        }
      ],
      "bom-ref": "urn:uuid:f216e5d9-9438-5c74-97e0-339a0e5e75ed",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.11-tuxcare.6 of @angular/upgrade."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:npm/%40angular/upgrade@11.2.11-tuxcare.6"
    }
  ]
}