{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c57feb47-481d-5f33-bcb4-c644919d76d6", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4", "type": "library", "name": "@angular/forms", "version": "11.2.0-tuxcare.4", "purl": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:e3a67748-0924-5d45-b477-95fd515b0816", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c518b8a7-504f-548a-bf35-5cdb0f1905fa", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:63528779-78a6-5c2b-837f-6ad6481ef0e3", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:eff73191-2026-5a20-b964-6a6cd88dc9c5", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:16024414-60ee-52b2-afe7-af40784446d8", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.4 of @angular/forms. not_affected \u2014 Target version 11.2.0 uses Node.js url.parse() API which does not perform hostname hijacking with protocol-relative URLs. The SSRF vulnerability (CVE-2026-41423) specifically affects versions using WHATWG URL constructor without the defense. The target's url.parse() produces empty hostname for inputs like '//evil.com', preventing the SSRF exploitation that requires hostname replacement." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ae553380-e749-5bcd-92d2-89847d2545e5", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1527a7e0-2793-5476-a397-94c2259ac0b5", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:318f8f16-dcec-56af-9777-dfbdec25d210", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a00ffec5-7ce8-58cb-a3f9-b2616e0fd08e", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.4 of @angular/forms. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-50170. The vulnerability exists in Angular's HTTP transfer cache feature, which automatically caches HTTP responses during server-side rendering (SSR) and reuses them during client hydration. This feature was introduced in Angular v16+ and does not exist in Angular 11.2.0. The target repository lacks the vulnerable code path entirely: no transfer_cache..." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3a419082-f8e5-5a01-bca5-f1962acb16cf", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e93c28e3-d09a-5f25-bced-9e8a13109366", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0b838982-5304-5da0-99ba-48c6ecf77daa", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fff3ff41-e4f3-5487-8f77-39120cbf547d", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6f489d42-26d8-5648-8714-e7a126961aac", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:07445c64-bc3c-5805-b505-d22f27f0f125", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:74d3c51e-c0e4-5c0a-8ace-39a70fe86434", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.4 of @angular/forms. not_affected \u2014 Version 11.2.0-tuxcare.2 is NOT affected by CVE-2026-54264. This version lacks the vulnerable code pattern - asset-group requests are reconstructed using URL-only (no headers forwarded), and data-group requests use browser's native fetch which strips sensitive headers per Fetch specification. The vulnerability requires a header-copying mechanism that does not exist in this version." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:27204795-fe98-5b75-9343-ef469f3db7cd", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.4 of @angular/forms. not_affected \u2014 Angular v11.2.0-tuxcare.2 is NOT affected by CVE-2026-54265. The vulnerability requires the Ivy template compiler pipeline's TwoWayProperty IR operation introduced in later versions (v20+). This version uses an earlier compiler architecture (View Engine + early Ivy) where two-way property bindings are desugared through the same parsePropertyBinding() path as one-way bindings, applying schema-de..." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cd645f34-af11-54ed-b15f-104983287ce7", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.4 of @angular/forms. not_affected \u2014 Angular v11.2.0 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature (introduced in Angular v16+) does not exist in this version. The transfer_cache.ts file and all related APIs (HttpTransferCache, generateHash, makeCacheKey, withHttpTransferCache) are completely absent from the codebase." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0ecc6573-f7cd-5db2-b92b-bc929b34e0fc", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ab40f892-a75c-5766-9c1f-e0a6bc6d493a", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5cc71a64-7cfb-5e86-a285-157b596ac064", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.4 of @angular/forms. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-68945. The vulnerability exists in HttpTransferCache, a feature for automatically caching HTTP requests during Server-Side Rendering (SSR). This feature does not exist in Angular 11.2.0. HttpTransferCache was introduced in Angular v16+ as part of the modernized SSR architecture. The target version predates this feature by multiple major releases. Only ..." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b5cfdf0a-028a-5e6b-989e-ed0938d39df4", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ea3cbb6a-9529-5a08-b600-e62dc9c03c6c", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.4 of @angular/forms." }, "affects": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/forms@11.2.0-tuxcare.4" } ] }