{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:22659750-56bd-575b-888c-51eb81672c7f", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4", "type": "library", "name": "@angular/router", "version": "7.2.11-tuxcare.4", "purl": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:1583bc85-c48c-5b9f-adfe-0bf1c3cea333", "id": "CVE-2021-4231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-4231 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d9174eb8-7ddb-55bd-99cd-9f60920ba53f", "id": "CVE-2025-66035", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66035 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c45873ac-15e2-5d1c-bc85-a643cc9b688d", "id": "CVE-2025-66412", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66412 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:21e3b108-1615-52fd-982f-cdb139b5006e", "id": "CVE-2026-22610", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22610 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6a4e727c-f8cb-5ed5-8cf3-f23fd59f23a1", "id": "CVE-2026-27970", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-27970 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:56248459-0d75-59c1-87ce-5ed163dffd9a", "id": "CVE-2026-41423", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41423 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:343e843d-c10f-58eb-a997-79d971163f01", "id": "CVE-2026-46417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46417 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:52865b58-153c-52b3-8878-2ffcc5b30bc6", "id": "CVE-2026-50168", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50168 does not affect version 7.2.11-tuxcare.4 of @angular/router. not_affected \u2014 CVE-2026-50168 addresses vulnerabilities in the WHATWG URL-based parseUrl implementation and allowedHosts validation feature introduced in Angular's CVE-2026-41423 fix. The target (v7.2.11) uses a completely different architecture with Node.js legacy url.parse() and does not have the allowedHosts feature. The specific vulnerable code patterns that CVE-2026-50168 patches do not exist in this ver..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ef9051e7-a593-565f-bdf3-3cda6704158e", "id": "CVE-2026-50169", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50169 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7657081a-8f1b-5f59-81f4-299df5d06a65", "id": "CVE-2026-50170", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50170 does not affect version 7.2.11-tuxcare.4 of @angular/router. not_affected \u2014 Angular v7.2.11 is not affected by CVE-2026-50170. The HTTP Transfer Cache feature that is vulnerable does not exist in this version. The feature was introduced in Angular v16+, and v7.2.11 lacks the transfer_cache.ts module, withHttpTransferCache provider, and provideClientHydration functionality entirely." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:833dc413-6f12-5c30-8940-e718489cf2a6", "id": "CVE-2026-50171", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50171 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b0c283e4-cabe-553a-ad99-09f7a4b0684b", "id": "CVE-2026-50184", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50184 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7792711a-19bf-5ffd-9a90-2c23416f7811", "id": "CVE-2026-50555", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50555 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c5190650-3a4c-529a-a66a-ebdcd2ca1a34", "id": "CVE-2026-50556", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50556 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:28b86e71-704c-554a-8173-15b5b07596db", "id": "CVE-2026-50557", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50557 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c02cfea9-8a82-534c-a354-491ffdf37254", "id": "CVE-2026-52725", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-52725 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c2ed19e6-92cd-5735-8c45-49d43e05c8f9", "id": "CVE-2026-54264", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54264 does not affect version 7.2.11-tuxcare.4 of @angular/router. not_affected \u2014 Angular 7.2.11-tuxcare.2 is not affected by CVE-2026-54264. The vulnerability concerns sensitive header leakage on cross-origin redirects in the request metadata preservation feature. This version predates that feature entirely - it strips ALL request headers when making network requests for assets, as evidenced by code comments and the absence of the newRequestWithMetadata method introduced in..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8cd68c96-11ab-5f68-bbb9-42cc17f51b6b", "id": "CVE-2026-54265", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54265 does not affect version 7.2.11-tuxcare.4 of @angular/router. not_affected \u2014 Angular 7.2.11-tuxcare.2 uses View Engine compiler architecture, not Ivy. The vulnerability (CVE-2026-54265) is specific to Ivy's template compiler pipeline where TwoWayProperty operations were missing from the sanitizer resolution switch. View Engine does not have TwoWayProperty operations; two-way bindings desugar early in the template parser to the same parsePropertyBinding() code path as on..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:97e8b09f-c049-5ac0-9bb4-2019fe9a1093", "id": "CVE-2026-54266", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-54266 does not affect version 7.2.11-tuxcare.4 of @angular/router. not_affected \u2014 Angular 7.2.11-tuxcare.2 is not affected by CVE-2026-54266. The HttpTransferCache feature that contains the weak hash vulnerability does not exist in this version - it was introduced in Angular 16." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8e31a67c-afd1-5e00-847a-6ef453bfd954", "id": "CVE-2026-54267", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54267 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:400cd8f5-8e1a-5279-9461-697345f80e9c", "id": "CVE-2026-54268", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-54268 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a12c77f0-cf48-5959-8144-c113f1500625", "id": "CVE-2026-68945", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-68945 does not affect version 7.2.11-tuxcare.4 of @angular/router. not_affected \u2014 Angular v7.2.11-tuxcare.3 is NOT AFFECTED by CVE-2026-68945. The vulnerability affects Angular's `HttpTransferCache` feature, which caches HTTP requests during Server-Side Rendering (SSR) for client-side hydration. This feature did not exist in v7.2.11 \u2014 it was introduced in Angular v16. The vulnerable file `packages/common/http/src/transfer_cache.ts` is absent from the target SHA (8c4c3a453736..." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0e6c0eb2-8bde-513d-8cb7-b146d9c73925", "id": "CVE-2026-69149", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69149 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ca7d8386-c844-545d-817e-a274ae00694c", "id": "CVE-2026-69151", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-69151 is fixed in version 7.2.11-tuxcare.4 of @angular/router." }, "affects": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:npm/%40angular/router@7.2.11-tuxcare.4" } ] }