{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:4d123838-827e-57a9-b538-9e5404fdf7bc", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/upgrade@11.2.0", "type": "library", "name": "@angular/upgrade", "version": "11.2.0", "purl": "pkg:npm/%40angular/upgrade@11.2.0" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:45ba7929-9898-53b5-9bc4-18bc351db324", "id": "CVE-2026-22610", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:c32fa301-b1fb-5e51-83e7-32a42cfdc062", "id": "CVE-2026-27970", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:0823c54a-74f8-50e2-8ae5-55d5e554c369", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 of @angular/upgrade. 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/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:7e38e05a-2195-502b-bbc8-e10c041739fd", "id": "CVE-2026-46417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:caa6a8a9-35bc-5e29-9ea3-65f1efd9c0d9", "id": "CVE-2026-50168", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:65380e18-31ef-5696-98b8-b9a1520b4c19", "id": "CVE-2026-50169", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:91f93832-e3a1-573e-ba5e-4fe9e6ff4ecf", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 of @angular/upgrade. 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/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:5e807802-3451-5523-a372-2559e3eba7b8", "id": "CVE-2026-50171", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:e572d5ab-4394-567c-baf2-087262d3d542", "id": "CVE-2026-50184", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:f238a7c5-bf51-5186-9dec-553d43be93be", "id": "CVE-2026-50555", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:51be756b-12a2-5221-a0ab-fa25a2050b2b", "id": "CVE-2026-50556", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:f36235e3-89de-54ba-9b47-8eba0ed183b4", "id": "CVE-2026-50557", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:0483595e-bad0-59f0-a504-d1f8f726017c", "id": "CVE-2026-52725", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:341e320d-a72c-5ae0-a770-859857e800ce", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 of @angular/upgrade. 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/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:d9e0a938-02d9-5ba2-93aa-85725d585e53", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 of @angular/upgrade. 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/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:9a92e316-d5b9-521c-85e8-a4cfef21da6f", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 of @angular/upgrade. 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/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:7da2c60a-803d-53cc-97f8-a3b29c4801ae", "id": "CVE-2026-54267", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }, { "bom-ref": "urn:uuid:f9fe7118-9f62-58e4-a41f-f4a9af99d62f", "id": "CVE-2026-54268", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@11.2.0" } ] }