CVE-2026-0778
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEnel 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Enel X JuiceBox 40 charging station exposes a telnet service on TCP port 2000 that lacks any authentication controls. Network-adjacent attackers can connect directly to this service and execute arbitrary code in the context of the service account, achieving remote code execution without any credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Scan for open TCP port 2000Use a network port scanner (e.g., nmap -p 2000 <target_ip> or PowerShell Test-NetConnection) to check if TCP port 2000 is listening on the JuiceBox device or within your network segment.Affected if Port 2000 is open and accepting connections, indicating the telnet service is exposed.
-
Attempt unauthenticated telnet connectionRun 'telnet <target_ip> 2000' or use a TCP client (e.g., netcat) to connect to port 2000. Observe whether the connection succeeds without prompting for any username or password.Affected if Connection succeeds and provides a shell or command interface without any authentication credentials.
-
Verify no authentication is requiredOnce connected via telnet to port 2000, attempt to execute a simple command (e.g., 'help', 'ls', or 'id') to confirm the service accepts and executes commands without login.Affected if Commands execute successfully without being prompted for credentials, confirming the service lacks authentication controls.
-
Check device network exposureReview firewall rules, access control lists, or network segmentation configurations to determine if TCP port 2000 is accessible from untrusted network segments or the internet.Affected if Port 2000 is accessible from network segments outside the trusted management zone, increasing exposure to remote attackers.
If TCP port 2000 is open and accepts commands without requiring any authentication, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable the telnet service if not required for management, or implement network segmentation/firewalling to restrict access to TCP port 2000 to authorized management IPs only. If telnet is required, apply vendor firmware updates when available.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0778 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data