{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:a1b2eb92-a1d4-518c-be5b-d814898e291c", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5", "type": "library", "name": "@angular/core", "version": "8.0.3-tuxcare.5", "purl": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:e1596c48-d9a8-53c4-b9a1-1c18c64c973b", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:30c96c04-43d5-5528-a529-a210229302e4", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:09a539dc-01c5-5168-8d08-6a4bcab683eb", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:371c1e87-f688-5769-b702-c1c7a401f8de", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:daa2767b-8cd9-518b-a3fe-a3bfff5af080", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:7b11e807-b537-5c62-83cb-5fd1bebda68c", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 8.0.3-tuxcare.5 of @angular/core. not_affected \u2014 The target Angular version 8.0.3 is not affected by CVE-2026-41423. The vulnerability requires WHATWG URL API (introduced in Angular 8.2.x+) to manifest the hostname override behavior. Version 8.0.3 uses Node.js legacy url.parse() which does not interpret protocol-relative URLs as having attacker-controlled hostnames." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:ea131ffc-685e-5eec-80cb-f44f1ab3c854", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:4113a480-ddec-5b0d-8a19-d97853ae33b5", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:b942516c-35ab-5e6f-9c4c-91eef59da1a8", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:62f0efe0-a2ae-56fa-846e-eec42bb783e5", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 8.0.3-tuxcare.5 of @angular/core. not_affected \u2014 The target Angular v8.0.3 is NOT affected by CVE-2026-50170. The vulnerability requires the HTTP transfer cache feature (packages/common/http/src/transfer_cache.ts) and client hydration mechanisms, which were introduced in Angular v16+. This version lacks the entire affected component." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:2a60bcd6-cf99-5b4c-8694-976e047891be", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:2349cf74-cad3-50c9-9485-97b38d2cde32", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:845669e7-35a6-566a-83ca-bd8f880b6f39", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:dacaafa1-6b3e-5a10-9946-d5179623bae0", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:6c8a60b0-76ad-5d29-b7c8-34aba4308f06", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:b9f52797-9af8-5488-a202-58ba58e946d7", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:03653d38-8aa3-5862-8fe4-b90b0d9b81d6", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 8.0.3-tuxcare.5 of @angular/core. not_affected \u2014 The target Angular service-worker version 8.0.3-tuxcare.4 is NOT AFFECTED by CVE-2026-54264. The vulnerability requires the service worker to copy and forward request headers during cross-origin redirects. This version never copies headers: the AssetGroup path creates fresh requests from URLs only (no header preservation), and the DataGroup path delegates to the browser's spec-compliant fetch A..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:d3a95406-85dc-5cbc-a028-17883e743100", "id": "CVE-2026-54265", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54265 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:0745fd3d-d7e8-5f3a-b676-b164ea6a1700", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 8.0.3-tuxcare.5 of @angular/core. not_affected \u2014 Angular 8.0.3-tuxcare.4 is NOT affected by CVE-2026-54266. The vulnerable HttpTransferCache feature with its weak DJB2 hash-based cache key generation does not exist in this version. HttpTransferCache was introduced in Angular v16+, while this target is v8.0.3." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:3835c32c-a370-5f73-b0ea-cc2d4f489ace", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }, { "bom-ref": "urn:uuid:6e6ff1e4-da26-5bc9-9df2-295bf46cbd7c", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 8.0.3-tuxcare.5 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@8.0.3-tuxcare.5" } ] }