# CVE-2026-0778: Enel X JuiceBox 40 Telnet Service Missing Authentication Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code on Enel X JuiceBox 40 charging stations via the unauthenticated Telnet service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-w47c-mgm4-6rq8

## What is CVE-2026-0778?

CVE-2026-0778 is a high-severity missing authorization vulnerability in Enel X JuiceBox 40, published on 23 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Enel X JuiceBox 40 Telnet Service Missing Authentication Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Enel X JuiceBox 40 charging stations. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the telnet service, which listens on TCP port 2000 by default. The issue results from the lack of authentication prior to allowing remote connections. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-23285.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-0778?


## How do I fix CVE-2026-0778?

No fix has been published for CVE-2026-0778 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0778 being exploited?

There is no known exploitation of CVE-2026-0778 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0778 and fix it if it is affected.

What it is: CVE-2026-0778 is a high-severity missing authorization vulnerability in Enel X JuiceBox 40, published on 23 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0778 in the wild and no public exploit code.

Affected product: Enel X JuiceBox 40. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0778/ (Markdown: https://insights.sbomify.com/CVE-2026-0778/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0778
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0778
- OSV: https://osv.dev/vulnerability/CVE-2026-0778

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0778/
Summaries are generated and may contain mistakes; the official description above is the record.