{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:fd7aaebf-42f3-5cb6-b8ca-0b2da2844007", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3", "type": "library", "name": "@angular/core", "version": "11.2.0-tuxcare.3", "purl": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:5299e0c1-3317-580a-9173-be0b7ca98e5f", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e9413a16-e154-56ff-bd83-2902c9d7e0c4", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:aeb4d914-95e1-5aa2-a4d3-a2c632992386", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9b3d0ad2-c8f5-5864-8f77-fcc7278fb75f", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:dbf1e2d5-91f9-5c97-afb1-7d6dca1585fa", "id": "CVE-2026-41423", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.3 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." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:16c42108-cdea-555c-8eec-f539791a3f5a", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4bd493f3-d982-586e-8c77-4abc12d781c1", "id": "CVE-2026-50168", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:fb934ae0-57da-57d5-b31b-cb0769a54dae", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5354a6e3-ff35-59c1-a0a5-0dd80e24707c", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 11.2.0-tuxcare.3 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:fd2cbf8c-1134-583f-ad57-577a8f4705fe", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1bdc9c40-2b5a-5d26-a25b-02e3645ddb08", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5e2082f8-24ac-5ae2-83e7-4c94649aea0e", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9fa541de-335e-50eb-b55d-74e8287fa5cc", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ce37e762-25fa-5966-88e2-3f680912efd1", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5f2e557a-1576-5d45-8b53-37182e0a5a3a", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:087574f7-9094-5bdf-adb9-89aefa719ad7", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 11.2.0-tuxcare.3 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." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d0251f7a-e2ab-5b02-99ba-aeb4f37c392d", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 11.2.0-tuxcare.3 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..." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:94c31169-845f-52ab-80a6-126bf00e63d9", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 11.2.0-tuxcare.3 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." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1a69d5fe-6257-55b7-b457-7c755ede49f1", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:059ad5ca-21b4-5e45-83f6-2a461fafbd72", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 11.2.0-tuxcare.3 of @angular/core." }, "affects": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/core@11.2.0-tuxcare.3" } ] }