{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:92390e5e-3010-5931-9cce-6e86b2627ab8", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3", "type": "library", "name": "@angular/upgrade", "version": "15.2.9-tuxcare.3", "purl": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:436af16c-2985-50d4-94af-7c5dc7c65000", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9cc2b8fc-5371-5906-9cae-0ca951e728e5", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a22bd28d-cb04-59bb-be10-90b11d43be03", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6a6c66fd-3f03-57a8-8321-490c8cbc14e0", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:48fd716b-17bc-58f2-98da-52456b870e80", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 15.2.9-tuxcare.3 of @angular/upgrade. not_affected \u2014 Angular 15.2.9 is not affected by CVE-2026-41423. The SSRF vulnerability via protocol-relative URLs was introduced in Angular 17.0.0 when the codebase switched from Node.js url.parse to WHATWG URL API. Angular 15.2.9 still uses the legacy Node.js url.parse which treats protocol-relative URLs ('//evil.com') as pathnames, not hostname overrides, preventing the SSRF attack vector." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2039aa45-6376-5967-b8b8-a293c20f6fdb", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4f67ad93-176f-58ba-837a-34dc300fa541", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e7debcbb-f73c-5a34-b54e-8c65266a1d4a", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e85445bf-d659-512f-89a1-be25be361b17", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 15.2.9-tuxcare.3 of @angular/upgrade. not_affected \u2014 no evidence captured" }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a4caa0c9-3913-59f6-84c9-9b3d61973a88", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bbdd41f6-e3ac-50c9-af54-d8a4c8a8acff", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3f2c8873-19c8-54e5-8a87-66398c66ac6d", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:aeb02e3f-77ce-592d-8f84-7f4f6df1f259", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d6d35e03-f49b-520c-84d4-4a51d510f52e", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f2adca07-5a29-5a7e-bf5c-7c50b69486ec", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ac2faa4f-e8d5-5b71-bfe5-670235a604d5", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:81222804-60e2-5172-8aad-4fb889145514", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 15.2.9-tuxcare.3 of @angular/upgrade. not_affected \u2014 Angular 15.2.9-tuxcare.1 is not affected by CVE-2026-54265. The vulnerability requires the new Ivy compiler 'pipeline' architecture with the TwoWayProperty IR operation, which was introduced in Angular 16+. Angular 15.2.9 uses the older compiler architecture where two-way bindings are desugared into separate property and event bindings, causing them to automatically receive the same sanitizatio..." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:035d9bc1-7960-5fa3-bedb-7a7efcee0e8d", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 15.2.9-tuxcare.3 of @angular/upgrade. not_affected \u2014 Angular 15.2.9 is not affected by CVE-2026-54266. The vulnerable HttpTransferCache feature does not exist in this version - it was introduced in Angular v16+. Without this feature, there is no code that hashes HTTP request properties for cache key generation, so the hash collision vulnerability cannot manifest." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:01e1355e-170e-5beb-8dfb-9f2f1ebd9007", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:05220bae-e840-5533-ba00-e9f6ca6f4bbc", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:232ecc7a-7cf3-5e73-a90b-51f4000f431b", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 15.2.9-tuxcare.3 of @angular/upgrade. not_affected \u2014 Angular 15.2.9 is not affected by CVE-2026-68945. The vulnerability exists in the HttpTransferCache feature used during Server-Side Rendering (SSR), which generates cache keys from HTTP request parameters. However, this feature was not introduced until Angular 16.0.0. Angular 15.2.9 lacks the entire HttpTransferCache implementation: no transfer_cache.ts file exists, no HttpTransferCache class, ..." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a9ac0c9b-dd61-582c-8fc6-512431876c28", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f9924691-f6e2-5071-86b9-f91b1871cf2b", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 15.2.9-tuxcare.3 of @angular/upgrade." }, "affects": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/upgrade@15.2.9-tuxcare.3" } ] }