{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:003f7b50-9d4f-5ad4-b9f2-4ff56d7d5788", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4", "type": "library", "name": "@angular/localize", "version": "11.2.0-tuxcare.4", "purl": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:9839ac03-8dd3-5c47-8a68-29d39f3a0a4f", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:afb23bc1-64fb-5379-b208-9e96213375b9", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dd6e70f2-bfb3-5b47-aaed-f329edddb7fb", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c06280d3-1f5f-5189-8a8b-92b7baa0ece6", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4d003818-141d-50ed-9ecd-f6ef051e677f", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.4 of @angular/localize. 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/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6808c65c-f9d2-5c26-adf9-be49e3f4254a", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:baa9913c-ce9a-58a1-a9ba-429675ed9b03", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:539df08e-5a1b-556f-bdd2-114e4519ff0a", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c2b78abe-9d97-5907-86f0-fcdc265b4ce6", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.4 of @angular/localize. 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/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:51a111e5-1012-5576-a773-0ed86c700196", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a1dafa0c-6bf0-5e92-af6e-6898b0331975", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:215a383f-3a47-5f3e-95d4-8fab6606dce1", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:244f1576-479c-5bbb-98cc-db0b87ed29a4", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:61de7d31-cd05-577e-aaf9-20a3439a19ac", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6fc8b432-4633-596c-a7b0-c38e76d47561", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2d7f7225-9b69-5985-9d8d-324d6293f81d", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.4 of @angular/localize. 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/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4687e563-b0b2-5979-86af-0fefa3f62548", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.4 of @angular/localize. 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/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5dc56a63-3cff-59c9-86f9-7c81592c07c0", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.4 of @angular/localize. 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/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4290e2cc-639d-56ee-8f5d-cd222aa9b00b", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d1360f0d-74a4-5215-9b65-6725b9a26904", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ec9fc4d0-ecbe-5025-bb7c-4add88be95b4", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.4 of @angular/localize. 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/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2eceeb55-8cb2-5e41-b99b-5653dc7a30e9", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:80f66ddd-7ae4-5e64-99a8-6b8346d246a2", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.4 of @angular/localize." }, "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.4" } ] }