{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:03b1e94b-e8c7-59fe-b9d2-9b384aada099", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21", "type": "library", "bom-ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21", "version": "5.2.11-tuxcare.21", "pedigree": { "ancestors": [ { "name": "@angular/bazel", "purl": "pkg:npm/%40angular/bazel@5.2.11", "type": "library", "version": "5.2.11" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-66412", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:5bfd5597-9aad-5657-abfd-2b80f5acdb29", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:50ed1b5f-eedd-5737-97e4-19236532a000", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 5.2.11-tuxcare.21 of @angular/bazel, and is fixed in 5.2.11-tuxcare.22." } }, { "id": "CVE-2026-101896", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:73da1bf5-c051-5d68-9c83-64bf1d1f7c02", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101896 affects version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-22610", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:80c11717-ef93-512c-a808-6d709d80df26", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:b9731bf7-f42e-531a-a0f5-b41eb5da372c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-46417", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:9dfbd534-21cf-55dc-be26-c8d770516900", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:ac9db9a8-ed55-5817-b5c2-91315540259d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-50169", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:3b91bd9f-9446-587c-9350-58686aa25f39", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-50184", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:21bb6518-f9df-5129-b3f4-8a9eaeb7b821", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:b060f6c1-ca29-5bd1-b738-87001aaf903a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:e1050bad-5963-5cff-acd1-1c0b7f843f06", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-50557", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:bebb7ae2-3617-5985-898e-82e273a703f2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-54264", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:4ec2a0c8-136b-5b1c-b93d-b7e5ff090c63", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54264 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-54265", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:281fb5cf-d9a9-545d-928a-1e29ac2c2a56", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:bfdc3e9e-0e74-5d6c-b7a9-4bc53dc969a1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-69151", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:5d9a31ba-f344-5d3a-bfcc-2f05528357b4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:ef78d47f-9f55-54c8-b0f8-3b14db8f21df", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 5.2.11-tuxcare.21 of @angular/bazel. not_affected \u2014 Angular 5.2.11-tuxcare.19 does not contain the vulnerable URL resolution code pattern described in CVE-2026-88056. The vulnerability requires the url.ts file with parseUrl function calling String.prototype.trim() and the relativeUrlsTransformerInterceptorFn HTTP interceptor, both introduced in later Angular versions (post-June 2026). The target version uses a fundamentally different architectur...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-88057", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:791e11d3-2bd1-5ebe-9f20-6419fa0d8153", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88057 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } }, { "id": "CVE-2026-88058", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:843092ee-7b52-5621-9092-d1ab6773c45b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88058 does not affect version 5.2.11-tuxcare.21 of @angular/bazel. not_affected \u2014 CVE-2026-88058 affects the domino library's HTML serialization (XSS via ancestor fallback raw-content tag injection in comments/processing instructions during SSR). The target Angular 5.2.11-tuxcare.19 repository declares domino 2.1.2 as a dependency but does NOT vendor its source code. The vulnerable code (NodeUtils.js serializeOne() function) lives in the domino npm package, not in Angular's ...", "justification": "requires_dependency" } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ], "bom-ref": "urn:uuid:b8c935b1-a04b-54c7-a9d2-ff1239b64018", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-88060 is fixed in version 5.2.11-tuxcare.21 of @angular/bazel." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/bazel@5.2.11-tuxcare.21" } ] }