{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:5751b623-62e6-503c-85bb-37ce31bb4ec5", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4", "type": "library", "name": "@angular/elements", "version": "11.2.0-tuxcare.4", "purl": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:ee814372-cef6-5b9f-92dd-463c831d874c", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ad2c2f7f-4a14-5401-b278-9c2acfa775c8", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1973ed62-75be-5e0d-8501-f974284cd516", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:03e3b48b-950f-5883-a5f7-3a261b3ffc44", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:518ed0d7-7f74-56c5-89a1-65bb216c52cb", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.4 of @angular/elements. 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/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d0ad2220-21a8-5d1b-b3e7-293741fd4dbc", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:79da3e1e-e30b-59fe-bcf3-48b2921bce7a", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8d1bf778-cc49-5fef-800c-70ce3ebe5cb4", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a5044a38-8563-506c-8404-fc2d9fa3f16c", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.4 of @angular/elements. 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/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:85c44c66-8869-5e8f-baf4-b1e7450be10e", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6b73103f-ea35-533e-afea-380cae7b71ba", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ac5bb493-6c53-5d84-b9f6-50b93030d222", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6d63203c-a18f-5579-bcd0-96cfe6b6b818", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1b8dbfb7-0630-5aca-b366-3b31c29b9614", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ed9ec2ac-86bc-538b-bff3-53b5833d5266", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b29b9a5a-e7c5-5e66-b4fe-9cf1d6a7611e", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.4 of @angular/elements. 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/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:217dd12e-45e3-5202-aba9-518567b21f1f", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.4 of @angular/elements. 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/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:36f64062-b487-5c6b-942b-3bd32bfd75cd", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.4 of @angular/elements. 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/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:914acf4d-2d9f-5796-968d-c1bb877f4e71", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:59613125-af27-561d-97ad-2b82d63d62db", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c9508c4a-7260-5895-a670-046dcf93768b", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.4 of @angular/elements. 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/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:71a9095d-a2a7-5484-8f14-ed13b1a07857", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8f35020a-84cd-53e5-b627-0eeb5753e5de", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.4 of @angular/elements." }, "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/elements@11.2.0-tuxcare.4" } ] }