{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:0ebfc383-9c3d-571a-b51f-75520175d13c", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/core", "purl": "pkg:npm/%40angular/core@11.2.0-tuxcare.7", "type": "library", "bom-ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7", "version": "11.2.0-tuxcare.7", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66035", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:99b9d052-6872-5a90-a7cc-3f9b2e3d6126", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:ffb78d1a-6896-58ee-b787-ad672c4452ad", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:ef86db15-6a7c-5433-a3c5-7093231cd7cc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:2833e678-cabc-51b8-a29f-44fa8138737e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:8a10db4c-076f-5f3d-96bc-1408a1fb927c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:39781e80-d18b-53f2-81d6-ff1c48e9db45", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:1d652db0-d425-575e-b7e8-5e0139f81dcd", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:08421bcf-b878-5319-a56f-33af29a8eba8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:f233a158-78fb-515c-bfa8-9541aaf36b5e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:66f26c0a-f007-54d0-8905-c4391f213236", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:91152c1d-17fb-5064-b735-1d7cc8dbd618", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:18432870-7c64-5b22-b144-a90fbbc82375", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:e580ea4a-4a9b-5648-8898-6f196b6060b5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:99f7214d-576d-5008-ad06-951f2322e4bf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:b6fa4d6e-e8c2-5bac-886f-430ccb4ac4a0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:92cced9d-d9ce-5032-92d9-8a383db28a59", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:9776f7c3-e24a-5f9f-8704-10e94ab2e1c4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:b4664b97-3941-599e-9913-f34d62c37146", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:fdb43a6d-1975-56a1-bb3f-5666524a0599", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:b103a8c1-736d-58b1-917d-30c841496b1c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:879114c7-100c-5960-a55d-d9b0a9f2efcd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:5102f9dd-a488-5780-8e2e-da3389e01d9e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:c6397e8d-b0a8-5427-9331-10e0f738eaa4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:94f1ed2a-9ad8-5c4a-95d3-a66f5394852f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:e5d90fb5-fa56-539f-8d66-bfa60d45cae3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:bca9d29d-121a-5d06-a674-1e8d46d9903f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:f828a15d-a3d6-5624-9570-526185176281", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:28903d17-20de-5cb4-b6e2-3ccd7cb8c61d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:60d1756f-cf7e-579c-9e03-878ac795dcaf", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.7 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.7" } ], "bom-ref": "urn:uuid:e1d8cba6-fc1a-5259-b63d-7987590d66ac", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.7 of @angular/core." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.7" } ] }