Vulnerability in S-102 Bathymetric Surface parser (CVE-2026-35001)
Summary
Vulnerability in S-102 Bathymetric Surface parser (CVE-2026-35001). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
OpenS100 through commit daa35b contains an integer overflow vulnerability in the S-102 Bathymetric Surface parser that allows remote attackers to cause a heap-based buffer overflow by opening a crafted S-102 HDF5 file with malicious grid dimension metadata. Attackers can exploit the unvalidated multiplication of numPointsLatitudinal and numPointsLongitudinal values in the S102_VG_BathymetryCoverage::Read() function to trigger a 32-bit integer wraparound, resulting in undersized heap buffer allocation and subsequent out-of-bounds writes that lead to application crash or arbitrary code execution.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35001 has been found in S-102 Bathymetric Surface parser.
Successful exploitation can lead to full system takeover. CVSS score: 7.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "S-102 Bathymetric Surface parser CVE-2026-35001" on the vendor's site.
CVE-2026-35001 (S-102 Bathymetric Surface parser) — CWE-122 / CVSS v3 7.0
Attack vector: local / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-122) exists in S-102 Bathymetric Surface parser.
Check the vendor advisory for the affected versions of S-102 Bathymetric Surface parser.
Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで S-102 Bathymetric Surface parser を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com