# CVE-2026-131807: United Chargers Grizzl-E Smart 40A OCPP GetConfiguration Stack-based Buffer Overflow Remote Code Execution Vulnerability.


- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-qp3m-73wq-hwg2

## What is CVE-2026-131807?

CVE-2026-131807 is a high-severity vulnerability in United Chargers Grizzl-E Smart 40A, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-131807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131807 is a high-severity vulnerability in United Chargers Grizzl-E Smart 40A, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131807 in the wild and no public exploit code.

Affected product: United Chargers Grizzl-E Smart 40A. 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-131807/ (Markdown: https://insights.sbomify.com/CVE-2026-131807/index.md)
```

## Sources

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

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