# CVE-2026-82118: Stack-based Buffer Overflow Vulnerability in HiRDB


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-4mh5-6qq4-42c8

## What is CVE-2026-82118?

CVE-2026-82118 is a critical vulnerability in Hitachi HiRDB Server Version 10, published on 27 Oct 2026. 

### Official description

Stack-based Buffer Overflow Vulnerability in HiRDB.

This issue affects HiRDB Server Version 10: from 10-00 before 10-12-01; HiRDB Server Version 9: from 09-00 through 09-66-22; HiRDB Server with Additional Function Version 9: from 09-00 through 09-66/V; HiRDB Server Version 9(32): from 09-02 through 09-66-22; HiRDB Server with Additional Function Version 9(32): from 09-00 through 09-66-/V.

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

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


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

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

## Is CVE-2026-82118 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82118 is a critical vulnerability in Hitachi HiRDB Server Version 10, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-82118 in the wild and no public exploit code.

Affected product: Hitachi HiRDB Server Version 10. 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-82118/ (Markdown: https://insights.sbomify.com/CVE-2026-82118/index.md)
```

## Sources

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

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