{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c1e2144c-d4b3-587b-8835-af67fe27fca7", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3", "type": "library", "name": "@angular/localize", "version": "15.2.9-tuxcare.3", "purl": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:031d1389-54a4-57b7-a62e-75a66eed1293", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:511f1efa-8b2d-52f9-a5c6-0c801c043b6e", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:424689e2-2993-5cfd-8aea-5bdeff712514", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e45c8e54-3f2d-50ef-be20-19687b5ca458", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:77bf4240-f301-56f2-afdb-35fc922e9593", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 15.2.9-tuxcare.3 of @angular/localize. 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/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bd0a1901-dde1-54c3-9728-e02bf1c39eb8", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8b3fb414-4d8b-540e-8d94-9d7129546fb3", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:72a37227-94f4-5356-a310-0af0b1e6ab89", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f56a8542-7ba3-5374-9930-2f10ab945aec", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 15.2.9-tuxcare.3 of @angular/localize. not_affected \u2014 no evidence captured" }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e27fcd25-59c0-54d7-a0e9-dd42ad748e3c", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e6e53997-d925-5cfc-91cb-289fdad4dec1", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0c09bada-db3a-56fe-9d46-c86e750c8afb", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:48326e5f-8568-542e-9e9b-1c86247a45cb", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bb910bfb-245e-5d56-9e78-e72a7418e707", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:86d6b53e-0485-5bb8-afa4-47160db72549", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6230f76d-b4e0-5a56-92b7-69909c0a20e3", "id": "CVE-2026-54264", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:429e8d3b-445e-506e-9f83-44da90776741", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 15.2.9-tuxcare.3 of @angular/localize. 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/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:95c4c16c-70cd-5aae-b908-db538aa06685", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 15.2.9-tuxcare.3 of @angular/localize. 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/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8f89099b-d458-5803-b07e-89a8cc93cde3", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:937302a8-c6a8-5bba-8916-dfb7e363e7f0", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a43c1a2a-797a-5de6-9bbd-351fba4d4b88", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 15.2.9-tuxcare.3 of @angular/localize. 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/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8548e842-153f-55a1-95b6-6ca1dfe8d146", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7bd82f85-7fd5-56ec-9c22-500a61cbc2ff", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 15.2.9-tuxcare.3 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/localize@15.2.9-tuxcare.3" } ] }