ETK-2026-855Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
eneo versions before 2.2.0 can permit resources to be transferred between different tenants because the resource mover does not enforce that both spaces belong to the same tenant. A principal with sufficient permissions in both spaces can gain control of resources from another tenant; tenant-scoped service keys may meet this condition when the related key-scoping flaw is present.
mitigation
Upgrade eneo to version 2.2.0 or later. Until the upgrade is complete, block cross-tenant move operations and restrict or rotate service keys that could be recognized as privileged outside their tenant.
fixed in 2.2.0
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-07 07:42Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-855
{ "etk_id": "ETK-2026-855", "cve_id": null, "display_id": "ETK-2026-855", "ghsa_id": "GHSA-j2c8-68q3-q67h", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Cross-tenant authorization bypass in eneo resource mover", "summary": "eneo versions before 2.2.0 can permit resources to be transferred between different tenants because the resource mover does not enforce that both spaces belong to the same tenant. A principal with sufficient permissions in both spaces can gain control of resources from another tenant; tenant-scoped service keys may meet this condition when the related key-scoping flaw is present.", "mitigation": "Upgrade eneo to version 2.2.0 or later. Until the upgrade is complete, block cross-tenant move operations and restrict or rotate service keys that could be recognized as privileged outside their tenant.", "vendor": "other", "product": "other:eneo", "affected": [ { "affected_notes": [], "affected_ranges": [ "< 2.2.0-rc.5" ], "ecosystem": "other", "fixed_versions": [ "2.2.0" ], "package_name": "eneo", "purl": null } ], "cwes": [ 639 ], "cvss_score": 8.7, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 62.633688316666664, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-10-07T07:42:48+00:00", "days": -14.42544022107639, "is_lower_bound": true, "measured_at": "2026-10-21T17:55:26.058071+00:00", "url": "https://github.com/eneo-ai/eneo/security/advisories/GHSA-j2c8-68q3-q67h" } } }
published 2026-10-07 08:15Z
last change 2026-10-21 17:47Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.