{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:3d21cdd0-2e27-53b0-8f94-bd30d9ae5839", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/elements", "purl": "pkg:npm/%40angular/elements@11.2.0", "type": "library", "bom-ref": "pkg:npm/%40angular/elements@11.2.0", "version": "11.2.0", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:beeb4bab-5dc4-5e82-a010-61f594b74d5a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66035 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.1." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:1d8b7b1a-2d44-5bb7-ae7a-b0bc627fd56e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66412 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.2." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:5ecb3f36-78b9-53a7-a26a-4492b792d971", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0 of @angular/elements." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:51197a45-52bc-589a-8277-cb4cb0f823b2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:53b9dee8-9e28-523c-b523-66259b255dab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:863a4aef-2656-5f5f-8d3e-16585d37798c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:ebd9ff90-9279-59bc-81bd-2a051055357e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:5defe8d1-4178-514a-bf89-9cf0900b90ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:cc252aae-2fbc-5a96-9990-c01db3e4602f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:cd2af6ba-199a-569e-b0f2-ee407cf2a349", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:94b4b950-5559-5b0b-9def-d28329b8a173", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:8bc3a0ba-417e-5248-a77c-7fa37aff389a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:05ad975a-dea5-5d79-86ec-b331dccc90dc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:22156be6-1856-5a68-aed1-4b643765481f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:1bcbaaba-9900-5246-a089-ad1d505e05c4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:d3e9061f-a3e8-5834-a241-ca1607d155d6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:a15bc5b0-92c2-5574-b2d3-689b12760571", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:a681d91d-60f0-534a-8e42-6c4c0ff874ca", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:623ddc8a-6069-580f-8e80-55f22ee0ce69", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:a9d0c3cd-7da7-5a0e-b6ba-4d90c6213876", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:fb733507-58b7-5595-9291-f5fddee0d175", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:81475b2b-cd99-5e76-973e-e370fcf9a2d6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0 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 ...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:25f685b3-a48d-54f5-ac73-7492220fde80", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.4." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:1a6fb638-6d41-5e1d-8b40-0c52c92d4862", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.4." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:c755156b-1161-57f4-94dd-be64b4b8182f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0 of @angular/elements. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-88056. The vulnerability requires a `String.prototype.trim()` call in URL resolution utilities (`parseUrl`/`resolveUrl`) that creates a discrepancy with WHATWG URL parsing, enabling SSRF attacks via Unicode whitespace. This vulnerable code pattern was introduced in Angular versions post-11.2.0 (appearing in 18.x-22.x) and subsequently fixed. Angular 11...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:6f30e2ba-52ae-55cf-9f78-a623070caa57", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:7f103fc6-9294-5805-b654-11cda22f457c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:d901e5e7-45b9-5429-a43b-065123ed06d7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0 of @angular/elements. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-88059. The vulnerability exists in HttpTransferCache when using hierarchical HttpClient configuration with withRequestsMadeViaParent() - features introduced in Angular 16+. Angular 11.2.0 uses the legacy Module-based HTTP API (HttpClientModule) and does not contain the HttpTransferCache component, provideClientHydration(), withRequestsMadeViaParent(), ...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ], "bom-ref": "urn:uuid:54c211f8-fec1-573f-943b-ad2973452152", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0 of @angular/elements, and is fixed in 11.2.0-tuxcare.6." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/elements@11.2.0" } ] }