{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:50092f0c-d6a4-544b-b2c4-c6f9b3a4a444", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17", "type": "library", "name": "@angular/http", "version": "5.2.11-tuxcare.17", "purl": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:6121b7cb-b53c-52cb-be91-fe4a0f46ba08", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:042bb298-7a32-5a55-a6c6-65a5b887c9bd", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:b580106b-86c9-5de0-b436-0b0d60307d3a", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:75a19583-07fb-51b1-a7b4-f5ceeafdd4f3", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:b2a130f8-4572-51a2-980e-cf57e82a1e05", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:4ca6f5b7-66fe-5ed1-8488-7c715f719c61", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:6c521bd3-d65b-54c0-be00-e1f13ccbcedc", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:785a0b09-5c2e-5952-b0f4-294b9daf46f7", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:8ee369c3-ac88-5229-b5cb-fc72494302a5", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:9b666977-8487-54d4-aff0-2d1a63522d29", "id": "CVE-2026-50170", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50170 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:acda7450-0450-543f-9b0d-c7ab1d60e274", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:7df628ad-18d1-597f-8059-fc7945b7a080", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:9bbf5965-bed7-5e2b-800d-0b95175fb2ba", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:b116d0cd-7196-5189-9e31-229111f110f2", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:c9f00748-af2a-56ef-b5ed-f56eae0dad6e", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:cb9c87f1-410c-50ff-8b3e-48a891fd2644", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:7e43a29b-92fa-5d66-995b-246096ce3489", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:9bbe5ed4-9dc8-59eb-afc8-8eabfd6f8ee0", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:9bd95293-bf9d-5efb-84f4-5fb851cfce04", "id": "CVE-2026-54266", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54266 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:2e5c9e92-3209-5702-94a9-969a8c15c661", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:26142ca0-e552-5d45-b239-c11631b9d8f2", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:5916d651-d74b-5adf-a237-a2a02d367686", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 5.2.11-tuxcare.17 of @angular/http. 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/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:530e3239-6e60-50ed-a9f5-8dde9e774048", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:baa4287d-24b4-547e-9b6e-6d128ad40ab3", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:257bc136-c0a9-5860-b953-477e7c0ee6c6", "id": "CVE-2026-88056", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.17 of @angular/http. 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/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:24403515-94bf-5a5e-b59c-ddc280d3f8c6", "id": "CVE-2026-88057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:9e0dc483-ad13-57af-8891-05a358980a24", "id": "CVE-2026-88059", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 5.2.11-tuxcare.17 of @angular/http. 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/http@5.2.11-tuxcare.17" } ] }, { "bom-ref": "urn:uuid:7e4c8291-e781-51c4-809c-8392f7d53466", "id": "CVE-2026-88060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 5.2.11-tuxcare.17 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/http@5.2.11-tuxcare.17" } ] }