{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:ff2cd6c7-3489-527c-afb1-2f0ea11d759a", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/compiler", "purl": "pkg:npm/%40angular/compiler@11.2.0", "type": "library", "bom-ref": "pkg:npm/%40angular/compiler@11.2.0", "version": "11.2.0", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:750c75fe-c05b-5647-8b23-ac4c7f4566ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66035 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.1." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:ece33f1a-8a1e-5d3c-8549-db5aad795225", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66412 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.2." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:dbb4b0ef-51a7-54f2-b716-3fc20564717d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0 of @angular/compiler." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:4074e27c-383b-5bec-ac2c-a4b5d10ebe1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:348c6275-b600-5c24-aae6-5fa5cbda3eaf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:94eac02e-977a-5d36-be9b-9caf7bbec1c7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:cb51291f-d0a3-5b47-a403-93407bf98eaa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:8161cb8b-359c-5182-a99b-237ee59f5dab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:739b7a7a-51d8-54f7-b4ba-449e55dbb7d1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:10040e02-9a88-5867-b752-5692665672f4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:26425fcc-fa01-5313-8f7b-bbdf1d38192c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:4c2223ce-1cb6-55d3-8d1b-7f49b8d0e50f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:a1be6bab-6489-5d3c-a96c-19b2da590520", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:aa5b5d19-4e52-5480-8530-9eb05c36c860", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:c5187ebf-0a57-57ef-8831-14732136ba9a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:14ff91e2-0b5c-5a5c-82a9-35ff72e09b7e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:075809ae-1abb-53b7-8469-902f3dd20404", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:79d7fa97-7c66-5f72-b9a3-1dbe0c437478", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:fda1e3f0-f353-59dd-8f05-31935285a4d3", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:6190daa1-4a96-55c5-87a4-ed8ca7f7f331", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:8bbad01e-d091-52ed-a9aa-a7d0eae845a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:f56ef67c-73d3-5f13-a45b-b19899dc12b3", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:b115defc-b0bc-5957-8aaf-81e3e4e8cbb0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.4." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:afe30bb5-d71a-5fde-b51b-5fe1da0f8b6b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.4." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:704a27f8-6ac8-5967-8a24-264f71f3f169", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:5af20023-e737-5cc7-9cb7-c817869db3fe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:7e2e69ce-0c9e-5d81-821c-2c280ff45c3b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ], "bom-ref": "urn:uuid:bf9eb767-4d00-5ebc-b074-a9cc0bd2e18f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0 of @angular/compiler. 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/compiler@11.2.0" } ], "bom-ref": "urn:uuid:f063ddcb-d02d-518e-9afd-ec6591708893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0 of @angular/compiler, and is fixed in 11.2.0-tuxcare.6." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0" } ] }