{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:5c3fa692-2e85-5a1e-974e-d998daa29721", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14", "type": "library", "name": "@angular/core", "version": "5.2.11-tuxcare.14", "purl": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:754c903d-6a22-5ec1-b666-9a59f164f5cb", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:1db8069c-2e38-5b6e-acfb-0307b50e8eae", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a3459ad6-a463-550e-b384-8ba989210a26", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:e59f6066-e730-5739-a372-6b841693a4b8", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:4222a06e-0983-5f4f-87a6-187716b74ffc", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:8faced0d-ea9a-58c7-8ba8-3d4fd56c577c", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:daeaab31-3f97-528f-ad12-7fa52c343c7b", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:33d933d0-dce5-5784-836c-ced1162f8fd6", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:eacbaf62-88a0-5dcc-a40b-649bc3ca985f", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:326d62be-bc2c-5577-9782-4d4e7d4cb089", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:a7f4fd81-293a-54d8-9fa3-f51d309a8487", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:54376a73-644e-529a-a4b6-0d732cf4b88e", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:b5a3970c-a589-5c40-9f5f-bff4034ccf02", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:f9bfde82-bcb2-5561-aa1c-3902ea48d96a", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:29ee38ee-7095-5087-9ac6-9725096cb8fd", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:cc959029-4049-5e2f-a28d-c6c21ab8d9fe", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:0a7b5f98-4b48-5345-a391-8b77e9c0d5ac", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:e4fcffd0-706f-5b46-86a5-c3e4bdcb9964", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:863c4106-e321-5a9e-bb02-d22ef05889b6", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:176d5e9e-47c5-5f9b-82ba-2e3e023bfe5d", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:6deda1d2-5f1a-543e-80eb-e4441c3e8a27", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:8f434305-f7cc-5518-ac3d-49c88d4dd80e", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.14 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.14" } ] }, { "bom-ref": "urn:uuid:a7ee2c2d-e724-5e29-a4ea-86ab8fc3c876", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:06eb8a94-025e-50bb-b43a-3d5de3fa83c8", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:dda1dbe1-9d2b-5de8-882c-421e89cf3bf3", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.14 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.14" } ] }, { "bom-ref": "urn:uuid:96858721-628c-533a-a2d5-0c4382bde95d", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }, { "bom-ref": "urn:uuid:bbc16175-4506-51c1-b404-b2bcad94ccac", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.14 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.14" } ] }, { "bom-ref": "urn:uuid:7156bcbc-a653-5894-a077-ae8e5c5e2cf0", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.14 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@5.2.11-tuxcare.14" } ] }