United Chargers Grizzl-E Smart 40A remote code execution via OCPP GetConfiguration overflow
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
United Chargers Grizzl-E Smart 40A EV chargers contain a stack-based buffer overflow in how they handle GetConfiguration requests in the OCPP protocol. An attacker on the adjacent network can exploit it without logging in to run arbitrary code on the device, though the flaw is typically used in combination with other vulnerabilities.
Written by a model
Original description
United Chargers Grizzl-E Smart 40A OCPP GetConfiguration 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 handling of OCPP messages. When parsing GetConfiguration requests, the process does not properly validate 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-28968.
Who should check
Teams operating United Chargers Grizzl-E Smart 40A EV chargers with OCPP connectivity
“United Chargers Grizzl-E Smart 40A EV chargers”
What to do
Workaround: The checked facts give no workaround or vendor guidance. The affected feature is OCPP message handling, so the vendor's guidance on limiting that feature is the place to look.
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-131807 (United Chargers Grizzl-E Smart 40A OCPP GetConfiguration 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-131807 (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):
- Grizzl-E Smart 40A device reachable over OCPP messages (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1033/)
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-131807 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131807 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-1033/
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-131807
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-131807"}.Affected versions
- United Chargers Grizzl-E Smart 40AGWM-07.029-03
cve.now Index
- 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
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131807 |
| Record | NVD · CVE-2026-131807 |
| Other links 1 | |
| Link | zerodayinitiative.com · advisories/ZDI-26-1033 |
Questions about CVE-2026-131807
Is CVE-2026-131807 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?
The flaw is a stack-based buffer overflow in how the Grizzl-E Smart 40A handles OCPP messages. Combined with other vulnerabilities, an attacker can execute code in the context of the device.
Source: zerodayinitiative.com
Which versions are affected by CVE-2026-131807?
Grizzl-E Smart 40A: version GWM-07.029-03.
Source: cve.now feed data
Am I affected, and how do I check?
The checked facts name only the Grizzl-E Smart 40A from United Chargers and list no affected version ranges. The flaw sits in OCPP message handling, so the relevant setup is a charger that is reachable over OCPP messages. To check a device, confirm the model is Grizzl-E Smart 40A and review its OCPP configuration with the vendor's documentation.
Source: zerodayinitiative.com
How do I fix CVE-2026-131807?
The checked facts list no fixed versions and no vendor patch identifiers. Check United Chargers' support channels for a firmware update or advisory for this flaw.
Source: zerodayinitiative.com
What if there's no patch?
The checked facts give no workaround or vendor guidance. The affected feature is OCPP message handling, so the vendor's guidance on limiting that feature is the place to look.
Source: zerodayinitiative.com
Related
- CVE-2026-131809United Chargers Grizzl-E Smart 40A OCPP Backend Configuration Authentication Bypass Vulnerability
- CVE-2026-131811United Chargers Grizzl-E Smart 40A OCPP Backend Configuration Hard-Coded Credentials Authentication Bypass Vulnerability
- CVE-2026-131813United Chargers Grizzl-E Smart 40A OCPP UpdateFirmware Out-Of-Bounds Write Remote Code Execution Vulnerability
- CVE-2026-131810United Chargers Grizzl-E Smart 40A Download of Code Without Integrity Check Remote Code Execution Vulnerability
- CVE-2026-131812United Chargers Grizzl-E Smart 40A FTP URL Path Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability
- CVE-2026-131808United Chargers Grizzl-E Smart 40A Wi-Fi Configuration Server Missing Authentication Vulnerability
No corrections so far. Something wrong on this page? Report an error.