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.
CVE-2026-68767
Score 6.1 from GitHub Security Advisory published 2026-08-22. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(high)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 22, 2026
Last Modified
August 22, 2026
Advisory Details (5)
Auto-updated Aug 22, 2026hashcat through 7.1.2 Off-by-One Out-of-Bounds Heap Write in fgetl() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/hashcat-through-off-by-one-out-of-bounds-heap-write-in-fgetlhashcat/src/filehandling.c at v7.1.2 · hashcat/hashcat · GitHub
https://github.com/hashcat/hashcat/blob/v7.1.2/src/filehandling.c#L1032-L1060commit 93b55d37d3b2 (hashcat/hashcat)
Fix landed in hashcat/hashcat commit 93b55d37d3b2 — awaiting tagged release
https://github.com/hashcat/hashcat/commit/93b55d37d3b2340013d4036f10181ddc67d44249GitHub - hashcat/hashcat: World's fastest and most advanced password recovery utility · GitHub
https://github.com/hashcat/hashcatCoordinated Vulnerability Disclosure - Off-by-One Null Byte Heap Buffer Overflow in fgetl() · Issue #4739 · hashcat/hashcat · GitHub
https://github.com/hashcat/hashcat/issues/4739Vendor Advisories for CVE-2026-68767(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 16:13 UTCEG score recompute
- 2026-08-25 16:13 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 15:57 UTCEG score recompute
- 2026-08-24 15:57 UTCGHSA enrichment
- 2026-08-23 15:40 UTCEG score recompute
- 2026-08-23 15:40 UTCGHSA enrichment
- 2026-08-22 15:24 UTCEG score recompute
- 2026-08-22 14:26 UTCEG score recompute
- 2026-08-22 14:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-68767?
When was CVE-2026-68767 disclosed?
Is CVE-2026-68767 actively exploited?
What is the CVSS score of CVE-2026-68767?
How do I remediate CVE-2026-68767?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-68767
Is Your Infrastructure Affected by CVE-2026-68767?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.