{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:efe18f3b-3da9-5881-8629-f08f4e2c3572", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19", "type": "library", "name": "@angular/core", "version": "5.2.11-tuxcare.19", "purl": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:4f077b1e-cd9c-5017-aa46-72b7dadff373", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:863cfe5a-f0cd-512b-a6eb-eb56bbd3e00f", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:e30fd3c0-ef89-5b91-9b17-69084a111123", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:62ffb83a-d673-5b25-a38a-8b068e49c352", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:58c83345-1ee9-5b1d-8d5d-cea9c9826ca0", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:cc0f32d2-e698-5963-85eb-84b08f3d571f", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:b9ca25f0-2fca-5408-bca0-e3377f90c550", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:e1934777-ae53-52e6-8e9e-b8debaf7d776", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:4d8d90c3-3bd2-5ff2-8034-d58ebc6d7b97", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:7f70023d-78a6-5273-b48b-cdf7dbfbd95d", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:9233d1b9-427a-5c52-ae4f-fe9d43c2ab53", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:70048b13-b4f0-5397-90a1-d76207846813", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:e466c4e9-89b9-5f9c-a694-5273bd12a2dc", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:2dd9a687-30b8-578c-8e2e-744d09a10be9", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:801e0e85-a8da-5216-b7a0-2d5f30074344", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:247b9822-5b66-5ccd-ba97-40821e5c56ff", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:eed2671b-2434-51bc-8dc0-efbef5250621", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:68228bb6-e3e3-5232-9b45-518e28d8d503", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:e7a4a505-8961-512b-a532-b993caf83b8d", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:f9e529dd-38f1-55cd-a07e-4dde0d573629", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:1099768e-2f65-5de8-8e92-e8a932941c8a", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:2f1d98e0-1362-50e6-adf6-2f779caf62cb", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.19 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.19" } ] }, { "bom-ref": "urn:uuid:8206b242-9233-54e6-88ec-17e77de00610", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:b7c37492-423d-5a14-a590-8cb8a70409ad", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:8b464567-8c7d-5af5-9ebf-d7b7f0b6aabc", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.19 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.19" } ] }, { "bom-ref": "urn:uuid:30eb9f84-72a5-5c44-8ac8-6a829caa1221", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }, { "bom-ref": "urn:uuid:87b77013-9eb8-5650-8ff7-db84e66eb0b8", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.19 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.19" } ] }, { "bom-ref": "urn:uuid:b42baf2a-3795-5878-83d8-afbcefea55e0", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.19 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.19" } ] }