# CVE-2026-42468: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted PCAP input due to improper validation in OVMS3.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-mf68-rrv8-6wmc

## What is CVE-2026-42468?

CVE-2026-42468 is a high-severity memory corruption vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow vulnerability in Open Vehicle Monitoring System 3 (OVMS3) 3.3.005. In canformat_pcap.cpp , the parser's phdr.len field is not properly validated, allowing remote attackers to cause a denial of service or possibly execute arbitrary code via crafted PCAP input.

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

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

It affects 1 product.


Products: Openvehicles Open Vehicle Monitoring System Firmware.

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

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

## Is CVE-2026-42468 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-37541](https://insights.sbomify.com/CVE-2026-37541/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-42469](https://insights.sbomify.com/CVE-2026-42469/): Memory corruption in n/a (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42468 is a high-severity memory corruption vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-42468 in the wild and no public exploit code.

Affected product: n/a. 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-42468/ (Markdown: https://insights.sbomify.com/CVE-2026-42468/index.md)
```

## Sources

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

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