{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:7f342e34-0fa2-53bf-b0f6-6d62cd4406af", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4", "type": "library", "name": "@angular/compiler", "version": "11.2.0-tuxcare.4", "purl": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:8631a809-c6f1-57c0-ab50-07fe408e1f34", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fa3662dd-7c44-5c77-b519-b9e02d89fe96", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7bce9d68-82ea-5c94-b5b7-f05b681eeb04", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dbb32427-9741-50bd-976a-1ecfd3fab752", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a560b5cd-373b-5441-afbf-4449756bf77a", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fac58ddc-6724-5b6c-84da-ae81d0811f4a", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c2e3d6df-52e4-5437-8162-b36631bdb2bd", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bb66a64b-a9a9-5f26-a9e2-39e1a64d96c5", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:06f8b449-4ecd-5e4a-bd2d-2a1d6c059a50", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:667f70bc-e633-5f0f-80b3-dbc21c478653", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7e5dc2ab-8d3b-5d50-96e5-6c6558531d6c", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c3758afa-1f5f-5dc8-be6c-3c907c76153e", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bfd20006-2af7-561b-b3bb-2948ab0e01a8", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4cad68f5-fb54-5e12-a525-a621e5f01d23", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:33c7f584-a553-5434-9788-aecb837b5b57", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3ee2c9b3-c10f-5945-b669-befe95f1a046", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e45009e0-996e-5018-a195-c8b42c96eb72", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.4 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:74069d23-76a7-5bc4-9966-c527bc0167f8", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.4 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." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ddc0a19c-bdb0-5f57-8b77-c59604412af8", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e48c64b4-985f-5e1a-81f0-20ad438a9f4b", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1b4e7cbc-935a-5bcf-86f5-7fc7f4b390b0", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.4 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 ..." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6e07683e-2f27-5ee2-9304-961cb5de6202", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6b029cbf-d9f9-5ad8-abeb-ed45d4f98ce5", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.4 of @angular/compiler." }, "affects": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/compiler@11.2.0-tuxcare.4" } ] }