{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c0e2eaea-135e-5cf0-90a5-1feaa1a003a3", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4", "type": "library", "name": "@angular/http", "version": "7.2.11-tuxcare.4", "purl": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:607d6e54-e5f0-56d9-8fac-70a87e342963", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b07809c7-61fd-5997-8a50-ef467e2673f6", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a68c9e15-abb7-5015-b362-a89e44d3e004", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b29db05d-b69d-5e8f-b51c-fb4696a5fbf7", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ae530f80-0e75-59c9-b2b7-5c49198a9978", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6ffe298f-db30-5554-84f2-02adf3af8796", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:40ba6e29-dc46-5275-986e-cae3f85289d9", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:668bf490-0f27-5009-acc1-a8eee0f1f5fa", "id": "CVE-2026-50168", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.4 of @angular/http. not_affected \u2014 CVE-2026-50168 addresses vulnerabilities in the WHATWG URL-based parseUrl implementation and allowedHosts validation feature introduced in Angular's CVE-2026-41423 fix. The target (v7.2.11) uses a completely different architecture with Node.js legacy url.parse() and does not have the allowedHosts feature. The specific vulnerable code patterns that CVE-2026-50168 patches do not exist in this ver..." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8c667f25-4f0b-5a94-bf3f-8cf247218481", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:73b1981c-4195-5edf-8ce3-2e7c6ca6d420", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.4 of @angular/http. not_affected \u2014 Angular v7.2.11 is not affected by CVE-2026-50170. The HTTP Transfer Cache feature that is vulnerable does not exist in this version. The feature was introduced in Angular v16+, and v7.2.11 lacks the transfer_cache.ts module, withHttpTransferCache provider, and provideClientHydration functionality entirely." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1442d68d-60cf-5af8-8514-c40ad93e0093", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a769009f-4cdc-55fa-a380-f993b40f1064", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f1df105f-845d-5b84-a6b1-d1842eb853da", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e41ea8d3-b298-50a6-861d-e7a5faada3eb", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c34034e2-6f76-5621-8582-7db879c58a4f", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4ac6c285-c9d9-5570-b938-7e5071a40973", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f268364d-3676-5ce6-8ea9-62cf165bbe58", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.4 of @angular/http. not_affected \u2014 Angular 7.2.11-tuxcare.2 is not affected by CVE-2026-54264. The vulnerability concerns sensitive header leakage on cross-origin redirects in the request metadata preservation feature. This version predates that feature entirely - it strips ALL request headers when making network requests for assets, as evidenced by code comments and the absence of the newRequestWithMetadata method introduced in..." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c25fdcfa-26db-5e51-9a1d-e625b31f5b2b", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.4 of @angular/http. not_affected \u2014 Angular 7.2.11-tuxcare.2 uses View Engine compiler architecture, not Ivy. The vulnerability (CVE-2026-54265) is specific to Ivy's template compiler pipeline where TwoWayProperty operations were missing from the sanitizer resolution switch. View Engine does not have TwoWayProperty operations; two-way bindings desugar early in the template parser to the same parsePropertyBinding() code path as on..." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:639da392-bef4-56bb-97ff-656be6775bb0", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.4 of @angular/http. not_affected \u2014 Angular 7.2.11-tuxcare.2 is not affected by CVE-2026-54266. The HttpTransferCache feature that contains the weak hash vulnerability does not exist in this version - it was introduced in Angular 16." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9d357725-30a9-5691-855b-252152e8e8dc", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d259fce5-3771-571e-b6ef-a198845455ac", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3cd5cd7c-2386-59a9-8030-35f96c5b0d52", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.4 of @angular/http. not_affected \u2014 Angular v7.2.11-tuxcare.3 is NOT AFFECTED by CVE-2026-68945. The vulnerability affects Angular's `HttpTransferCache` feature, which caches HTTP requests during Server-Side Rendering (SSR) for client-side hydration. This feature did not exist in v7.2.11 \u2014 it was introduced in Angular v16. The vulnerable file `packages/common/http/src/transfer_cache.ts` is absent from the target SHA (8c4c3a453736..." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e35e46cd-ae84-5cdc-ae27-396af6aee367", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9297f513-24c3-5993-95d1-7b2f4072f518", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.4 of @angular/http." }, "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.4" } ] }