{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:fc4615b0-b313-57f4-8980-ec613265f9d7", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/localize", "purl": "pkg:npm/%40angular/localize@11.2.0", "type": "library", "bom-ref": "pkg:npm/%40angular/localize@11.2.0", "version": "11.2.0", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:af599547-f054-5676-ae30-423db29a2931", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66035 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.1." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:999bdf4b-938d-5bf2-bccc-8dd7bd6cd6e9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-66412 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.2." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:e1c9c5a2-a1b1-54b9-9bea-7ebea826dde5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0 of @angular/localize." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:0f0b117d-2d7d-5f03-8f1a-a8b59457379d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22610 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:e1139010-86f4-52c7-acf2-2f7bc48adb4f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-27970 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:b5b9f8e0-6c3b-5d1b-8960-b60084d6a2fc", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:f98b4398-6b1a-5754-a2ba-c6c97431e3b4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46417 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:f2cf5b12-d936-5a5d-ac57-3c6ef1123ecd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50168 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:9462e85d-e33f-53f4-a564-10a7262fa648", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50169 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:9d172790-fb19-5ac4-918b-8c77a2a2f162", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-50171", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:5ac965c7-76f4-572a-afbb-e38c13866be3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50171 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:a26d7a2d-f035-5b03-9966-8e69d82b9eea", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50184 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:61cc9327-3f63-5ae2-9068-fec44b5ad488", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50555 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:8c4fd3d3-c119-5690-92de-11f4bd4d1605", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50556 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:d764426d-d60a-54f0-af28-5ded311e2b13", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50557 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:5b5e0254-784b-5acf-bf04-72dd0f30a4fe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-52725 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:adff4a25-df06-5b3f-8082-847420c50405", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:ccbccc8d-fe4c-5f63-bb11-a5dff0a559f8", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0 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...", "justification": "code_not_present" } }, { "id": "CVE-2026-54266", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:7cf44402-996c-5846-9570-0be02c859825", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0 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.", "justification": "code_not_present" } }, { "id": "CVE-2026-54267", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:a15f5a8f-bc64-5c98-9aab-1c632b15b715", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54267 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:63bb3add-a6bb-5e1e-965d-6714b34de672", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-54268 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.3." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:93867ae4-e035-5d07-a847-936ec6060a30", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0 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 ...", "justification": "code_not_present" } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:1a15571c-fd1c-5773-a552-71842ffa58ff", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69149 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.4." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:eb03d92b-322b-5c61-b372-edb5abfb11a2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-69151 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.4." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:50d7c2d4-9241-59cd-a4d7-7bac9e933d37", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0 of @angular/localize. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-88056. The vulnerability requires a `String.prototype.trim()` call in URL resolution utilities (`parseUrl`/`resolveUrl`) that creates a discrepancy with WHATWG URL parsing, enabling SSRF attacks via Unicode whitespace. This vulnerable code pattern was introduced in Angular versions post-11.2.0 (appearing in 18.x-22.x) and subsequently fixed. Angular 11...", "justification": "code_not_present" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:1308e5bd-84fb-57d0-8f9c-6ca291352a1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:a5acfcb7-2300-5107-be09-72b23bbba3a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:e280a0fb-a194-50d5-95e1-0eb3adce422a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0 of @angular/localize. not_affected \u2014 Angular 11.2.0 is not affected by CVE-2026-88059. The vulnerability exists in HttpTransferCache when using hierarchical HttpClient configuration with withRequestsMadeViaParent() - features introduced in Angular 16+. Angular 11.2.0 uses the legacy Module-based HTTP API (HttpClientModule) and does not contain the HttpTransferCache component, provideClientHydration(), withRequestsMadeViaParent(), ...", "justification": "code_not_present" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ], "bom-ref": "urn:uuid:0e7acefe-19f1-507a-9f7e-fff12009c3c2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0 of @angular/localize, and is fixed in 11.2.0-tuxcare.6." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/localize@11.2.0" } ] }