# CVE-2026-68767: hashcat through 7.1.2 Off-by-One Out-of-Bounds Heap Write in fgetl()

> Attackers can trigger an out-of-bounds heap write in hashcat by providing a specially crafted input file, potentially leading to code execution or crashes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/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:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-68767, GHSA-vgv2-whp7-2895, UBUNTU-CVE-2026-68767

## What is CVE-2026-68767?

CVE-2026-68767 is a medium-severity memory corruption vulnerability in hashcat, published on 22 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's fgetl() function in src/filehandling.c writes a null terminator one byte past the caller's buffer when an input line is exactly the buffer length. Attackers can trigger this out-of-bounds heap write by providing a hash file, potfile, or wordlist containing a line of exactly HCBUFSIZ_LARGE bytes.

Weakness: CWE-193 (Off-by-one Error)

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


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

Apply the vendor's patch.

## Is CVE-2026-68767 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68767 is a medium-severity memory corruption vulnerability in hashcat, published on 22 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-68767 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-68767/ (Markdown: https://insights.sbomify.com/CVE-2026-68767/index.md)
```

## Sources

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

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