{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:3160a82e-9b16-58cf-b52d-c32210c26261", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16", "type": "library", "name": "@angular/core", "version": "5.2.11-tuxcare.16", "purl": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:dfb3f7da-2e8d-5659-b582-5ff95bdda4f1", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:d05eb3c4-79c2-577d-89a6-4c6eb59d458d", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:6cb174fd-1453-51a4-a8cb-7785fbacf67e", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:2862d293-9a5e-5310-8afd-a0dda755d612", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:ea1e3eb1-2ec6-5470-af2f-2a8a441893f8", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:b23e45db-f443-595d-976e-02673f55f089", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:3b4540e2-f825-579c-a41e-76fd70f93fb3", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:66fcccde-4ae6-59cd-99e8-3a2bb977ca78", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:40ebc993-72fd-51c4-91ed-34049d4cad70", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:f871422e-92bd-5244-8ae9-c8ec42f3dd2a", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:a1184770-bda6-58d0-9423-392e8a15856d", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:2532953b-2a46-54f6-9351-c696d68e6e61", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:56c8ee38-946a-50f6-a3d3-e0baf6acb9c9", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:d44b15b1-ba01-5493-be7a-f9520fb882df", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:c8a1e20d-4597-584b-9029-b905a53b0213", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:25dc0d12-8459-518a-9dc4-1180beea1963", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:703dc9f0-2d3f-5706-a0bf-cc0eba3cadc5", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:f07e6533-d05c-578c-b804-d999e73fdd46", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:ed1161f9-13dc-5241-9f9b-3ff0a83335c0", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:2fd45bea-a471-5774-a7e1-abb1c22dea75", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:35955fb8-55bc-52be-a925-05579f63894f", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:c8c52a35-d36f-5104-8208-e294f7138ea4", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.16 of @angular/core. not_affected \u2014 Angular 5.2.11 is NOT affected by CVE-2026-68945. The vulnerable component `HttpTransferCache` does not exist in this version. This feature was introduced in Angular v16 as part of the modern SSR hydration system. Angular 5.2.11 only has the basic `TransferState` API (a generic key-value store for manual state transfer), not the automatic HTTP request caching interceptor that contains the vulne..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:90eda778-1708-5823-b944-ccc79b3fa62d", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:96071a3d-b2ea-5178-bab1-21963e9b36c1", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:fef9a492-03ae-5043-96a5-61cbb4a305a8", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.16 of @angular/core. not_affected \u2014 Angular 5.2.11-tuxcare.19 does not contain the vulnerable URL resolution code pattern described in CVE-2026-88056. The vulnerability requires the url.ts file with parseUrl function calling String.prototype.trim() and the relativeUrlsTransformerInterceptorFn HTTP interceptor, both introduced in later Angular versions (post-June 2026). The target version uses a fundamentally different architectur..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:b555d112-9710-56f5-a36e-ec4b7a4e2855", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:fadd36ef-9063-5f60-b6e7-0a5daf77650e", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.16 of @angular/core. not_affected \u2014 Angular 5.2.11 is NOT AFFECTED by CVE-2026-88059. The vulnerability requires HttpTransferCache with hierarchical HttpClient delegation (withRequestsMadeViaParent()), features that were introduced in Angular v16. Angular 5.2.11 predates these features by approximately 6+ years and contains only a basic HTTP interceptor architecture with no automatic response caching mechanism. While TransferStat..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }, { "bom-ref": "urn:uuid:19a36797-253c-5dd2-ace5-90df2f2eafb7", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.16 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.16" } ] }