{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:d315ccd6-f9d0-517a-8f73-5c5a0334fd98", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/core", "purl": "pkg:npm/%40angular/core@11.2.0-tuxcare.5", "type": "library", "bom-ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5", "version": "11.2.0-tuxcare.5", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:0d0fda98-0334-5712-b955-bfff29b1f40f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:28258535-025f-5dce-92dc-595045fbf45b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:12ee2774-3de2-5b4b-80b2-9fc688fcad2c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:2a0f1792-54d2-57e2-bdb0-d46d5290c09a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:a4dbeaf6-cc3e-510c-8e6e-82047714235e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:66575d37-860a-501d-96cb-e48a15349972", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:8b9f974e-9d0e-56be-beaa-bf11c1af6b20", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:5fd92b82-4df3-5845-a1b0-36b09126a1b9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:af0f0527-0151-5951-8c42-01647300d89b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:0b5c8f1a-dd19-519a-8ccc-7b885d4e09e4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:43d0d57e-0f85-52d2-a240-1ee72fed084d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:3aade534-0693-5d75-b3b6-4a796e89fdd6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:2d6fcefe-7bfe-5a51-b6b5-a4e80ae81537", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:26a57dd4-8b30-56e1-a784-adfdfdd72a53", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:d9b54adf-9710-522c-a005-29556b279e01", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:dc9a468c-f35e-51f8-a529-418015076e65", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:0d374fad-2fd2-5cbc-9a21-9ba85a654247", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:01aa4165-c7c2-5eb5-bafd-e65aa0e5cbee", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:33d9c484-7afa-59a1-9fb6-44bef5d72a54", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:3457c526-4899-5a6a-a8cd-c0cc9285e000", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:641a120b-93b7-512d-9acc-4af44d16801d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:49215192-d365-5ad7-9a6c-919644b5535b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:11a92663-48de-5891-ade0-7b6d97b1c7f3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:c03b7d5e-c65f-557e-90f1-0b9434b436f2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:e50fe63b-7463-5e9c-b3e9-64b9689eeafb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88057 affects version 11.2.0-tuxcare.5 of @angular/core." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:7304dac2-cf05-50b1-968e-5546fbe3cd7f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.5 of @angular/core. 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/core@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:8208bdd4-2e24-54d6-8c09-3672bc019b90", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0-tuxcare.5 of @angular/core." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.5" } ] }