{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:68090047-fa08-5597-9815-2fcafa1d343e", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/http", "purl": "pkg:npm/%40angular/http@7.2.11-tuxcare.8", "type": "library", "bom-ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8", "version": "7.2.11-tuxcare.8", "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.8" } ], "bom-ref": "urn:uuid:90295e05-1cbd-5faa-a1e5-29c025c8bcdb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:6c39371c-e321-5c39-bfc1-9b5943465410", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:e26e3f7f-db09-5c4d-91d6-ef4692d94e8e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:76625860-fbb1-5cab-b791-b4026bb1b438", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:b0af0bc8-dd8d-5929-b1ca-33666e8b9009", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:4c2bfafb-c8f3-5fc7-86e0-844cfc72010e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:a96049ae-7b11-5cae-9d5f-b90e3adc035e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:67818d7b-6cab-5fa8-bb48-1b06a52e17c2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:5861ef9b-4735-563c-8a90-8eee0928030d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:c95c903e-8d2e-5d62-b20e-9f5c5a9fde17", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:36e43aab-de2a-5466-887e-bff5a1078cb2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:36fc8d6b-d3c1-5e61-863b-a2725ed1080f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:27dae165-4e0f-5e0e-a71b-38a6a1eb6016", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:ce22b2b7-4223-5316-9a5f-e6340b778f5e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:eb98ba51-6314-53c6-a369-b9923c47f87c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:ed820359-b4e2-5158-8dba-2da8219e9beb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:5777c839-5c7f-5767-b0d9-6356278dcc28", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:15f767ab-4098-5c11-9fe5-0fe11f4f6323", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:d6645a10-0f61-5919-8eed-88c8506178fe", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:9c6fdf2f-0674-528d-9699-5f9dd99b6599", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:b09a4d63-b852-5039-a36f-36a69de11627", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:377b8020-2567-51f5-9bf8-a53362df94dd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:ed829bb2-ee2d-51c2-a275-d6a07c2ce6e4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:60cc899a-8f29-509c-ac2a-da174ea8f222", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:cbee57ee-a48e-545d-bdfc-e4174fc8448e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:172960e5-87a8-56b1-980a-36fcbbbfecf2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:d629300b-7a67-5c9e-b4eb-da869cc3f20d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:31dfeda6-9989-5efb-84b0-711524447a98", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:158f8ab8-d84d-5c3b-a994-b22f015da065", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ], "bom-ref": "urn:uuid:e4cebc87-4453-566f-9a06-2ffeb64b7332", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.8 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.8" } ], "bom-ref": "urn:uuid:95bacf6e-d174-5133-99aa-7d0d7e56b5eb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 7.2.11-tuxcare.8 of @angular/http." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/http@7.2.11-tuxcare.8" } ] }