{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:45752e07-8808-5b48-9346-f7a67f38736e", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/localize", "purl": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6", "type": "library", "bom-ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6", "version": "11.2.0-tuxcare.6", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:9de7bcc0-3e97-54ad-825d-319d9c2b7660", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:3b437296-c9b3-593b-b099-2ab9953578f5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:a542ac0b-da96-5d42-a5e4-a02183961d50", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:deb1afbc-ea11-5d19-829c-fc5774810335", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:b000ca4a-6ad6-5bc5-bd66-8fb0cb3735dc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:81611657-47ae-5dc6-a3c5-6d2ddf20d0a5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:4d1fb893-54ca-5d61-9150-4bdaba9e3010", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:5e8f92b6-8eb1-5542-9d66-e1d0f282d913", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:91012d1b-8a0b-528d-bfa5-1b80c9e2cfba", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:594c59ac-ca3f-5c86-a065-d9aed4e65d5d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:06ea01ff-1309-5b80-8f03-8901bd4be2ea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:60e9fb2f-0d1f-591e-9ea5-7124b287d6bb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:ab563619-8772-5d89-a51a-9e2d3b0a81a7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:99c731c9-2feb-589d-8a2c-a9042c0bae49", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:f3f57c5a-a81c-56cc-8fbb-7a2d3d799eb0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:ce8fe4ed-11a7-5907-a833-38bdcabe41a5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:96f978b2-3cd0-5b83-aa3f-49a1aa65f727", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:b9ffea4a-2ebd-5296-a730-3b459a20dac4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:a9fecd3e-7a36-5d14-9490-ff42e3ad7647", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:0a46713f-8ffc-5b2e-b57a-e2189452b2b3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:5fd965ed-729f-5387-bd8e-8a2aa542542c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:ab6aa217-b546-5ed1-945c-d93215fad511", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:e91d3e6e-8553-5b56-a8de-97c83c42e247", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:263940a1-714c-5d15-9429-98f9f8d2f376", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:1da74b1f-29df-5010-9098-485a04496e0e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:2ba2c9af-4184-563f-82a9-2cba089189c1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:2dd1505a-99b1-5609-8c41-42cbf86b44e8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ], "bom-ref": "urn:uuid:cab7d83c-d0bd-59a6-a68a-cc82cced6e4d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.6 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-tuxcare.6" } ], "bom-ref": "urn:uuid:43aafd53-dbee-508d-bcf3-3c117695ae9c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.6 of @angular/localize." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/localize@11.2.0-tuxcare.6" } ] }