{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:b72bd9a6-bf0c-54a6-a15c-24b455d2b8b1", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/language-service", "purl": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8", "type": "library", "bom-ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8", "version": "11.2.0-tuxcare.8", "pedigree": { "ancestors": [ { "name": "@angular/language-service", "purl": "pkg:npm/%40angular/language-service@11.2.0", "type": "library", "version": "11.2.0" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:76bbfc9b-bf29-546d-88b0-fbff067cd141", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:50fc5696-4197-58dc-914f-287f8924f6b3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:5f71dc7e-bdd1-5262-bbb5-5a7ead0cef23", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:658763af-e8ca-5a95-a505-213b26781caa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:a5cbc1eb-f26e-5055-998d-5df6de96ec13", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:48094524-8493-54d3-9aaa-ddcb09f0753b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:e340b8b3-619e-5429-8714-71e42eab924a", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:ad062878-eb66-58ec-bb10-715caa315b03", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:220d8a4e-3955-5823-9e6a-ec656431329d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:b033e912-2913-555c-addd-4742de0fad7f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:648b2c24-f05c-50c2-86ae-4def12d032d6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:a732dbbe-225c-55bd-8883-ef52564d7ee1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:aabde536-03f4-5100-a3bd-fd7dc110a0fb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:d08f43e3-8dde-5af1-b191-2d8833657d62", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:0b8d62e7-947e-56e0-a1f3-184dcc47d820", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:cbe112c0-6699-5d79-9049-892fce13f0f1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:49758f9f-a6f5-56e8-9b54-32d7ed0fc92a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:9dda6b40-5e0e-5b59-9cc7-97742604e460", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:c01c7f0a-39d5-5e2a-99c9-5c3f3f41e504", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:4d01b5fa-0a93-5d0c-a890-ab4604da9eee", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:471dfdb2-8307-528f-958d-47aff5c5ac70", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:a39e446d-5533-5e18-9561-268b914a06c8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:0b855f26-1695-5eb9-a2f6-3d7fc163129d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:264b53af-e802-551e-afdb-38658e8f574f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:777690b0-2346-5b42-bd99-b1e0dc1e6e2c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:39b3155e-357b-5924-a428-0f10f78baa75", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:1038e20a-dcc3-52d1-99ed-5c9286046549", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:8f1a776a-18b9-5813-855c-d1b8caa87229", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:0c580934-d1ba-5735-b426-1a42c2b18e20", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.8 of @angular/language-service. 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/language-service@11.2.0-tuxcare.8" } ], "bom-ref": "urn:uuid:8648cdba-9402-5e1c-aeb0-6c5e6e60a67d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.8 of @angular/language-service." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.8" } ] }