Skip to main content
Menu
CVEs

United Chargers Grizzl-E Smart 40A remote code execution in FTP URL path parsing

Affects the United Chargers Grizzl-E Smart 40A EV charger during its firmware update process, where FTP URL paths are parsed. No fixed version is listed.

CVE-2026-131812Published November 19, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The United Chargers Grizzl-E Smart 40A EV charger has a stack-based buffer overflow in how it parses FTP URL paths during firmware updates. A attacker on the adjacent network, without logging in, can run code on the device, though the flaw is typically used together with other weaknesses.

Written by a model

Original description

United Chargers Grizzl-E Smart 40A FTP URL Path Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of United Chargers Grizzl-E Smart 40A EV chargers. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the parsing of FTP URL paths during firmware updates. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of the device. Was ZDI-CAN-28960.

Who should check

Teams running United Chargers Grizzl-E Smart 40A EV chargers, including firmware update and network-adjacent deployments

“affected installations of United Chargers Grizzl-E Smart 40A EV chargers”

zerodayinitiative.com

What to do

Workaround: The checked facts name no workaround. Until the vendor provides guidance or a fix, the vendor's own instructions for the firmware update process are the source to follow.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131812 (United Chargers Grizzl-E Smart 40A FTP URL Path Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131812 (entry last updated 2026-11-19):
Affected:
- United Chargers Grizzl-E Smart 40A: versions GWM-07.029-03
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Firmware update process that parses FTP URL paths (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1034/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-131812 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131812 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zerodayinitiative.com/advisories/ZDI-26-1034/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131812
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131812"}.

Affected versions

cve.now Index

14Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 7.5, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131812
RecordNVD · CVE-2026-131812
Other links 1
Linkzerodayinitiative.com · advisories/ZDI-26-1034

Questions about CVE-2026-131812

Is CVE-2026-131812 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A stack-based buffer overflow occurs when the charger parses FTP URL paths during a firmware update. The advisory says this can let an attacker run arbitrary code on the charger.

Source: zerodayinitiative.com

Which versions are affected by CVE-2026-131812?

Grizzl-E Smart 40A: version GWM-07.029-03.

Source: cve.now feed data

Am I affected, and how do I check?

The listed product is the United Chargers Grizzl-E Smart 40A, and the flaw is in the firmware update process that parses FTP URL paths. No affected version range is given, so compare your charger's firmware version with the vendor's notices and check whether its firmware updates use FTP URLs.

Source: zerodayinitiative.com

How do I fix CVE-2026-131812?

No fixed version or vendor patch identifiers are listed in the checked facts. Check the vendor's channels for a firmware update that addresses this flaw.

Source: zerodayinitiative.com

What if there's no patch?

The checked facts name no workaround. Until the vendor provides guidance or a fix, the vendor's own instructions for the firmware update process are the source to follow.

Source: zerodayinitiative.com

No corrections so far. Something wrong on this page? Report an error.