# CVE-2026-35001: OpenS100 S-102 Parser Integer Overflow Heap Buffer Overflow

> An integer overflow in the OpenS100 S-102 parser allows attackers to execute arbitrary code or crash the application via a crafted HDF5 file.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/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:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-636c-c9vm-prrj

## What is CVE-2026-35001?

CVE-2026-35001 is a high-severity vulnerability in OpenS100, published on 13 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

OpenS100 through commit 2b1dafc contains an integer overflow vulnerability in the S-102 Bathymetric Surface parser. An attacker can supply a crafted S-102 HDF5 file with malicious grid dimension metadata that causes memory corruption when a user opens it. In the S102_VG_BathymetryCoverage::Read() function, the numPointsLatitudinal and numPointsLongitudinal values are multiplied without validation, and the 32-bit result can wrap around, producing an undersized heap buffer allocation. Subsequent writes past the end of that buffer cause a heap-based buffer overflow, leading to an application crash or potential arbitrary code execution in the context of the user who opened the file.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

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


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

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

## Is CVE-2026-35001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35001 is a high-severity vulnerability in OpenS100, published on 13 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-35001 exists.

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

## Sources

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

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