{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:2394af81-2ca7-5ce5-9e11-ef38a85ad946", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/forms", "purl": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3", "type": "library", "bom-ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3", "version": "7.2.11-tuxcare.3", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-4231", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:390064c7-36fe-5d86-ab95-77fab80d7711", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:76211868-6378-5200-8c30-c1d034e2e24c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:9980faf2-e53b-570e-a0cc-32e451f3345d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:7afa1a9a-1c7a-53a7-8b67-ee5bbc0e9b3f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:c5b7bb02-d59a-5109-bee1-f0300b730f04", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:72d7d98c-9d74-55af-b782-604195e21245", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:08ab3030-3d77-5ea3-869a-e560f00ce3fb", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:f20ae95b-9884-5a0b-a58c-94851fa24481", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:95417bce-21fd-5ea2-b67c-8d0879e10a47", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:1c3e933d-135c-5101-b229-599b89dbf24d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:2a2a0b12-a6b0-5a24-9794-229a707f7a0e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:2ff11ed4-9594-5932-93bf-e3780adbba01", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:15d924d3-647e-5442-af25-4f8474a8479a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:5e5a2886-6642-54fd-aecd-8256727b62c1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:8f133c07-6707-5fe4-b847-9c7448bd3be5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:8b2fdaa5-9ef1-5cdc-b7bb-f0f05759d643", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:86ea18a4-9306-58f9-949d-35685bfc9772", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:66f8b26b-2072-580b-be9f-a6a0a791c22a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:9c0a8b2e-bdfd-58a4-a393-ee1152cf7ed9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:f7c9e6d2-4572-5500-9e03-dc0604e92585", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:a9829bd7-8b1b-5424-acb2-a1d7f3c51621", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:b0a1cbe3-ddab-5ddd-a58e-0f706bcd3420", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 7.2.11-tuxcare.3 of @angular/forms, and is fixed in 7.2.11-tuxcare.4." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:4a7bdd75-a8f9-5e91-adb7-5c38ac114da7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 7.2.11-tuxcare.3 of @angular/forms, and is fixed in 7.2.11-tuxcare.4." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:0897aab3-1c12-583d-b59f-d35680e9b564", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:2daeb606-80fb-58f3-9bf2-7448e76be4b4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 7.2.11-tuxcare.3 of @angular/forms." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:ede9a456-f44a-5bd0-937b-6dde7ed066fb", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 7.2.11-tuxcare.3 of @angular/forms. 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/forms@7.2.11-tuxcare.3" } ], "bom-ref": "urn:uuid:78f600ab-a99b-5cf7-882f-5eb856222adf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 7.2.11-tuxcare.3 of @angular/forms." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/forms@7.2.11-tuxcare.3" } ] }