{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:09532fe9-ef7c-57ae-8732-bedf966d9e17", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/http", "purl": "pkg:npm/%40angular/http@7.2.11-tuxcare.7", "type": "library", "bom-ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7", "version": "7.2.11-tuxcare.7", "pedigree": { "ancestors": [ { "name": "@angular/http", "purl": "pkg:npm/%40angular/http@7.2.11", "type": "library", "version": "7.2.11" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:ed78012e-8825-5da8-817d-27e6ca9c67f6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:501ead0a-e6e3-507c-a12f-ca64c00ba75f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:e23d1795-667f-55d4-83ef-3b63abea8b4f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:050bf280-3cf0-5641-a7ca-a9c6310b2851", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:9ae71caf-ff5c-5326-82bb-648193f1da2e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:31bf2853-71fd-5caf-904b-fb5b715856aa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:b8aa7dc3-407e-5d07-a7f5-4cd3bfb768ab", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:2bdf1069-c2ed-5286-b8f2-a48956c5399c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:6a1c8f64-8d2f-5ce6-a68e-42609b4add19", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:2c8d9c1c-ee94-5a82-b047-a2401c3b0080", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.7 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:c9b57c7e-ee40-5c0e-b6b4-aed08fbc1bcf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:7c825a83-c85b-5bdf-8e6a-d178fe11fdc3", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.7 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:147f24fe-4e9e-50e6-884b-d944d0afa3f3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:a8a3bd0a-36e8-59f9-bb2f-bf5a5663b4f9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:93046ca6-9ce2-5400-9d0a-345f6cd1ad09", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:0e9eebe0-8772-50ab-af72-829a262d140e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:8ad8722f-2c51-51d8-817e-16f9fe293604", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:edf138a5-b7fb-54b8-ab2a-3fdc6f4ec5f4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:80a44ee1-6581-59b7-947e-15fed20b7208", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.7 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:9f2bc050-a193-5ffa-bc1c-8a0c0cc193a1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.7 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:bafd9e54-9880-5264-833c-8e2d9fa700c1", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.7 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:b38c7e86-6311-5037-93a0-6779d3c494b9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:0ecfa15c-d8e5-50ef-a6d8-968818670f6f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:6f33a51d-4e8e-569b-b4bd-baa30581c7ac", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.7 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:06a8e1b6-51b2-5e28-9f2c-1c867119669a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:6893032a-ccde-5a9a-a244-1d05a9a81ed0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:6d2029fb-caf0-5900-b4f2-ed50364d2b28", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.7 of @angular/http. not_affected \u2014 Angular 7.2.11 is not affected by CVE-2026-88056. The vulnerability requires calling String.prototype.trim() on URL strings before WHATWG URL parsing, creating a discrepancy that enables SSRF. This vulnerable code pattern was introduced in Angular 14+ with a new url.ts file containing parseUrl() that called .trim(). Angular 7.2.11 uses a different parseUrl() implementation in location.ts that d...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:05d99e25-c6e0-54c7-867f-b0aa97f22ef4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:5ec804a6-07a7-51ed-bd3f-56b6c0fe69fc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:255f5037-794b-5162-8fe7-2c39fba28936", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.7 of @angular/http. not_affected \u2014 Angular 7.2.11 is not affected by CVE-2026-88059. The vulnerability requires HttpTransferCache interceptor and hierarchical HttpClient configuration APIs (withRequestsMadeViaParent, provideHttpClient) that were introduced in Angular 14+ and do not exist in this version. While TransferState exists in 7.2.11 as a basic SSR state transfer mechanism, there is no automatic HTTP response caching to T...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ], "bom-ref": "urn:uuid:e1999ab5-52e2-5722-ae93-c0c4d8a5d392", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.11-tuxcare.7 of @angular/http." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.7" } ] }