{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:41e0f158-432a-53ac-a219-594867467c37", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:d2c06723-ceb8-5989-89bd-8183b97c285d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:a0f91669-812f-5024-84d2-3ea2396fe8f7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:bc2cf38b-c7a5-5968-ac1c-021beb992414", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-101895 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:ae8c0ae3-7f09-5cef-8e34-71f46a67463d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:1da960dc-c596-5e80-aaad-8090b6315df8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-27970", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:43c83119-54fc-56c6-b59c-bca17a01f602", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:b3fa60aa-244e-5452-8de7-bdb4813b5773", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:0d0c2e92-aaa1-5db1-be3a-60391d51e936", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:3ebec7e4-89d2-5024-aa51-8e0bc4516ed4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:1054ae2f-3bce-5da0-8a6f-29e1246f4af1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50170", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:d4d2170c-c1e1-5c72-816e-cf4ad9df4153", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:31671e94-ec4b-5540-acc6-cffd79c8d541", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:02414f3e-9c4a-58c1-a0c2-fcce1b3b42c7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:e3d68b2e-d4da-5a57-b7b9-577b74c8ced7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:6da395e7-6890-5e36-877d-bf393b9967ef", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:f4b601b8-06f9-5166-aa9e-38ad326c5c50", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-52725", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:a1c73d96-0394-5f68-b090-e8093d792994", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:7456b527-bf9a-5e4d-bd04-fd243819855d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:9f127ca1-0fce-5278-998a-93638df2da62", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:f91bd955-b335-57f3-81d0-71af296f6440", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:29b27e72-5823-57c5-9b69-f82087eb794a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-54268", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:17292bb5-73ec-5e1b-9b57-d4e71c402338", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-68945", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:4e88cd9a-98e7-5143-9313-72b0a70ecf75", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:487645b9-a6f0-5e62-980d-19afa0ea25d1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:89244f56-f1b6-5b3d-b051-7326c6623cc8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:15b7b79b-de00-52fd-a1b0-9f5b9eb273e3", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:f775e45c-694c-5b80-bac7-20d6f47c0f08", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:9be07a36-273c-509a-8e31-1985a028f387", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88058 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } }, { "id": "CVE-2026-88059", "affects": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:7450982f-3eec-525c-a440-7115c03a0695", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88059 does not affect version 11.2.0-tuxcare.7 of @angular/bazel. 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/bazel@11.2.0-tuxcare.7" } ], "bom-ref": "urn:uuid:fa934592-0c15-5382-8f3d-10de61ea7b69", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 11.2.0-tuxcare.7 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@11.2.0-tuxcare.7" } ] }