{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:4419ca3a-dd70-5843-ad67-24775edce3d4", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "@angular/platform-server", "purl": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5", "type": "library", "bom-ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5", "version": "11.2.0-tuxcare.5", "pedigree": { "ancestors": [ { "name": "@angular/platform-server", "purl": "pkg:npm/%40angular/platform-server@11.2.0", "type": "library", "version": "11.2.0" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-59052", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:ab6880f0-a2f7-5119-8be7-275c091670e9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59052 affects version 11.2.0-tuxcare.5 of @angular/platform-server." } }, { "id": "CVE-2026-101895", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:0d12126e-b7c4-5221-8462-ba356475a00c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-101895 affects version 11.2.0-tuxcare.5 of @angular/platform-server, and is fixed in 11.2.0-tuxcare.7." } }, { "id": "CVE-2026-111754", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:c8ce5743-3c20-5397-90f8-cb2468085645", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-111754 does not affect version 11.2.0-tuxcare.5 of @angular/platform-server. not_affected \u2014 Angular v11.2.0 is not affected by CVE-2026-111754. While the underlying data flaw exists (ServerPlatformLocation can store protocol-relative pathnames like '//evil.test' after dot-segment normalization), the exploitation mechanism described in the CVE does not exist in this version. The CVE targets the @angular/ssr package's automatic redirect-on-navigation-mismatch behavior, which was introdu...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-41423", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:d211cca5-ceaf-52c8-87f6-d9af4d77c20c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41423 does not affect version 11.2.0-tuxcare.5 of @angular/platform-server. 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/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:2528587a-6059-56d4-85b9-805485e24fd5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 11.2.0-tuxcare.5 of @angular/platform-server." } }, { "id": "CVE-2026-50168", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:4e5406bf-02ca-5ebd-9b76-1ece1a96612d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50168 is fixed in version 11.2.0-tuxcare.5 of @angular/platform-server." } }, { "id": "CVE-2026-50555", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:660d6a1b-4581-50da-9197-508e56bbacdb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 11.2.0-tuxcare.5 of @angular/platform-server." } }, { "id": "CVE-2026-50556", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:cf6f634d-976b-5cbf-bf46-9ab64b3c24a3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 11.2.0-tuxcare.5 of @angular/platform-server." } }, { "id": "CVE-2026-69149", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:eb0ab662-9768-5d52-9519-d3e2a444b3a3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 11.2.0-tuxcare.5 of @angular/platform-server." } }, { "id": "CVE-2026-88056", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:e784c609-e52e-513e-9dbd-a34d19a540b7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-88056 does not affect version 11.2.0-tuxcare.5 of @angular/platform-server. 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-88058", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:de4099fb-1e3b-54e8-865c-45f660c28a1e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88058 affects version 11.2.0-tuxcare.5 of @angular/platform-server, and is fixed in 11.2.0-tuxcare.6." } }, { "id": "CVE-2026-88060", "affects": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ], "bom-ref": "urn:uuid:ab3bb925-9f3c-585d-8c32-cd8409e8a213", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-88060 affects version 11.2.0-tuxcare.5 of @angular/platform-server, and is fixed in 11.2.0-tuxcare.6." } } ], "dependencies": [ { "ref": "pkg:npm/%40angular/platform-server@11.2.0-tuxcare.5" } ] }