# CVE-2026-111158: EarthScope libmseed through 3.5.4 Heap Out-of-Bounds Read via ms3_detect

> Attackers can cause a denial of service by supplying a truncated miniSEED buffer to the libmseed library, triggering an out-of-bounds read and crash.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111158, GHSA-p3hv-2xrm-x5px, UBUNTU-CVE-2026-111158

## What is CVE-2026-111158?

CVE-2026-111158 is a medium-severity memory corruption vulnerability in EarthScope libmseed, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

EarthScope libmseed through 3.5.4 contains a heap out-of-bounds read vulnerability in ms3_detect() in parseutils.c that reads past truncated miniSEED 2 record buffers. Attackers can supply a 40 to 47 byte buffer passing MS2_ISVALIDHEADER to msr3_parse() or ms3_detect(), over-reading up to 8 bytes and potentially crashing the process.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-111158 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111158 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111158 is a medium-severity memory corruption vulnerability in EarthScope libmseed, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111158 exists.

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

## Sources

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

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