{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:bbae4d17-6f65-54ed-ab97-51ba4aa38187", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11", "type": "library", "name": "@angular/core", "version": "6.1.10-tuxcare.11", "purl": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:78b6d85e-01dd-50e2-9008-811512fce418", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:29f6abdd-8c3b-5a07-8c42-bdb47f4397be", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:70003d3c-3bd5-53d2-ac96-0552f1c5e222", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:d05f4fe9-3fa9-5d79-a3fd-1624af28f783", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:b5719f86-bb8c-5934-b763-50ba98c766f8", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:79c9ed1d-4a4a-5cef-99a0-2f2c8f4e82b1", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:a542fbc9-a6ec-5ef8-bc03-9097d30862a6", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:f9d10b3a-eb0a-5079-b480-a2f3725026a7", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:b8918e62-b783-58a4-9159-6da78487ec3d", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:6dae8970-eedd-5ba8-b942-cbcf50acd982", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:bcdd63fe-55b2-5e8f-9231-089a68a77edb", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:ae0873e4-bfb3-589d-830a-d31cd20f5add", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:054ac4af-eeac-597d-ad8b-34f980f85ef5", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:927bb795-82c3-5943-b286-a11c6ca7b684", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:33f25e87-8d6f-51ce-aa46-d0863fca477c", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:dec8df70-d27c-5c1b-b54b-d90961b8cd54", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:0ddefd06-401c-556e-92b3-da0ae8282b0c", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:5654db0b-dff0-5d21-a92c-cf12d53bd8eb", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:8896455f-a4e2-5579-abc0-8f8aac3fc392", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:c3192dc2-8bb3-50bf-ba44-38b9c993cbb4", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:7004eb20-26dd-5513-ae13-cfc89e50be4b", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:232f9179-37f5-5cf6-8c79-c6dbca131471", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 6.1.10-tuxcare.11 of @angular/core. not_affected \u2014 Angular 6.1.10 is NOT AFFECTED by CVE-2026-68945. The vulnerable HttpTransferCache feature does not exist in this version \u2014 it was introduced in Angular 16.0.0 (April 2023), more than 5 years after Angular 6.1.10 (2018). The vulnerable file `packages/common/http/src/transfer_cache.ts` and all related APIs (`provideClientHydration`, `withNoHttpTransferCache`, `sortAndConcatParams`) are completel..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:f29a5476-3599-569d-b72d-619df713f079", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:735f92cc-a000-5b55-9719-4699265b4f74", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:9cf584cd-6137-5b19-be07-4eb3abdb1da1", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 6.1.10-tuxcare.11 of @angular/core. not_affected \u2014 Angular version 6.1.10 is not affected by CVE-2026-88056. The vulnerable code pattern (url.ts with parseUrl using String.prototype.trim() and relativeUrlsTransformerInterceptorFn interceptor) does not exist in this version. These components were introduced in later Angular versions (post-6.1.10) and subsequently fixed in August 2026. Version 6.1.10 predates the vulnerable SSR URL resolution arc..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:8c5cc572-a90c-5a70-8835-156ac02c87e2", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:8f5046c9-d85f-5d97-a5f9-c79cac03c223", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 6.1.10-tuxcare.11 of @angular/core. not_affected \u2014 Angular 6.1.10 is not affected by CVE-2026-88059. The vulnerable HttpTransferCache feature, withRequestsMadeViaParent() delegation API, and modern hydration system (provideClientHydration()) do not exist in this version. These components were introduced in Angular 16+ (circa 2023), while the target version is from Angular 6 (2018). The vulnerability requires automatic HTTP response caching duri..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }, { "bom-ref": "urn:uuid:60e1032d-3562-5a4d-a8b0-160fe56504b7", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 6.1.10-tuxcare.11 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@6.1.10-tuxcare.11" } ] }