{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:9846ea41-845f-5062-b39c-6dde7f70c534", "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.9", "type": "library", "bom-ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9", "version": "11.2.0-tuxcare.9", "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.9" } ], "bom-ref": "urn:uuid:d2e43617-aa25-5ef7-9d76-35696fa5dbce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:ec589f2c-b9e5-552e-83d9-cd28144c83b3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:e8fff002-6095-5878-8e39-2321a20d8895", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:a4fdc80a-451d-530d-bd4d-937273dbee00", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:fdd8a73f-f4b3-5e71-9d54-a230ab075459", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:3a367146-3708-5768-a647-2d2a52769c30", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:359a6462-a387-5d0b-8c28-0dc1120ed6f6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:7bf3849c-7c8e-5e96-88ad-cfc4f27a80bd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:167b11bf-0224-5b6d-a618-4a531cd3e556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:d79964ec-b7aa-5dcf-bbe2-928f1ad1c85d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:f5fa924e-986f-5156-b64d-321e961f9428", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:165503e4-8f0c-5318-89cc-b99548bf570f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:f2a1a706-e2c5-5c36-b2d4-18975f996dbd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:ee8fcdf0-de06-5fa2-a4c0-ae114d244e31", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:1909af42-e1c3-5d70-b931-db3241c036fb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:3a0c5106-c001-5e49-8bc0-86e4058dff28", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:c1756518-4cc1-5216-8933-03c03e79140e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:f42189a2-f3c6-55ae-b0a5-2999ab93bfe7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:f952121a-b674-5143-a4dd-a6cd0b76c1b0", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:c428a77f-c688-54f4-8e2c-89f1b7f23a0d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:9f293edb-548d-5346-ad85-f766cd91ab16", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:ac35417b-b68d-5952-9837-a660e2022cbc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:0534983f-9332-53c8-b479-8e34b5c41217", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:6cdcf102-9c3c-5925-9af2-f6ed4009bacd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:39935a89-2f7a-5f49-a6d1-2217bac479d7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:97e0b356-2905-5733-96c3-cd439987377b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:5ea88552-d075-5e54-9814-449212db3625", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:d86533cc-e468-513b-8501-749387fea18b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ], "bom-ref": "urn:uuid:85220993-581f-5943-9514-8669defeea72", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.9 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.9" } ], "bom-ref": "urn:uuid:c8a3bc25-41d4-561d-a15f-35616cd797ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.9 of @angular/language-service." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/language-service@11.2.0-tuxcare.9" } ] }