{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:cd39f282-b874-5ef4-bff3-b9b5280d3076", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4", "type": "library", "name": "@angular/common", "version": "11.2.0-tuxcare.4", "purl": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:5c1be92f-06db-5029-8363-75fbc64b1f9c", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c367280d-2123-5804-a39e-b962df951244", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a94c7054-aecf-523e-9957-a33322b9af41", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c933f7f8-3690-5085-9c07-1ca717319117", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ebd37080-5d21-51fc-a5f0-9eb5eb27f955", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.4 of @angular/common. 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/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4a70e857-aaef-5c55-a520-57786b956938", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:27d15f62-cfb9-5d3a-897c-d0386af46b6d", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:46624fbf-bc7a-5dfa-a484-8886a9ecfa2c", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ee90e723-260c-55a7-bb7c-a2399463ace6", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.4 of @angular/common. 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/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1932bfa8-6a75-5cf7-a4b2-30b86c14bcb0", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c22e5efb-411e-5171-871f-5421fb05a5a1", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6a583df6-b3c5-547f-824a-aa9e48188220", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9535f1f7-65c2-5442-9b24-bf99b59f6d07", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:80bd6d93-be87-5d66-a3aa-5cd43b545340", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:12c25b8b-d8ae-50d5-8d62-dc50dfa9bc9b", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:79509400-0155-5986-a304-e1cb3fa88ceb", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.4 of @angular/common. 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/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d632b7fb-4019-5723-afdd-1bb8e9cfddb2", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.4 of @angular/common. 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/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3ccc1c3d-4f45-5aaf-935a-283f3fd258f3", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.4 of @angular/common. 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/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:45812a96-50bf-5a2c-8e26-60fc86181935", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:53830a47-09d4-583c-8796-c6ba6044b86d", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:17f29330-0a57-5059-a5ff-0ece0ae23bc3", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.4 of @angular/common. 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/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:84fde413-3c36-5d5e-a92c-d1ca315291ad", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d0d74814-e42d-5fc1-bffe-f4a17cda52ae", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.4 of @angular/common." }, "affects": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/common@11.2.0-tuxcare.4" } ] }