# CVE-2026-68765: hashcat KeePass KDBX v4 Module Heap Buffer Overflow via Token Field

> Attackers can trigger heap corruption in hashcat's KeePass module via oversized input, potentially leading to code execution or crashes.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:A/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-jfqq-rfm8-8frm, UBUNTU-CVE-2026-68765

## What is CVE-2026-68765?

CVE-2026-68765 is a medium-severity memory corruption vulnerability in hashcat, published on 17 Aug 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

hashcat master branch builds after v7.1.2 contain a heap buffer overflow vulnerability in the KeePass AESKDF/KDBX v4 module (module 34301) that allows attackers to corrupt adjacent heap memory by supplying an oversized ninth hash field token. The module accepts up to 600 hex characters for the ninth token field but decodes it into a fixed 256-byte buffer with no length check, allowing a maximal input to write up to 44 bytes past the buffer boundary into adjacent esalt fields and heap chunk metadata, potentially enabling heap corruption or memory access violations.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

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

## Is CVE-2026-68765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68765 is a medium-severity memory corruption vulnerability in hashcat, published on 17 Aug 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: There is no known exploitation of CVE-2026-68765 in the wild and no public exploit code.

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

## Sources

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

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