# CVE-2025-24956: Memory corruption in OpenV2G

> An attacker can trigger a buffer overflow via crafted EXI data, leading to memory corruption and potential code execution in applications using OpenV2G.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 11 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-357m-v762-qj4c

## What is CVE-2025-24956?

CVE-2025-24956 is a medium-severity memory corruption vulnerability in Siemens OpenV2G, published on 11 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in OpenV2G (All versions < V0.9.6). The OpenV2G EXI parsing feature is missing a length check when parsing X509 serial numbers. Thus, an attacker could introduce a buffer overflow that leads to memory corruption.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-24956?

It affects 1 product.


Products: Siemens Openv2g.

## How do I fix CVE-2025-24956?

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

## Is CVE-2025-24956 being exploited?

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

## Other vulnerabilities in Siemens OpenV2G

- [CVE-2022-27242](https://insights.sbomify.com/CVE-2022-27242/): Memory corruption in OpenV2G (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24956 and fix it if it is affected.

What it is: CVE-2025-24956 is a medium-severity memory corruption vulnerability in Siemens OpenV2G, published on 11 Feb 2025. 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-2025-24956 in the wild and no public exploit code.

Affected product: Siemens OpenV2G. 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-2025-24956/ (Markdown: https://insights.sbomify.com/CVE-2025-24956/index.md)
```

## Sources

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

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