# CVE-2026-42482: Memory corruption in n/a

> A stack-based buffer overflow in hashcat allows attackers to execute arbitrary code or cause denial of service via crafted rule files or long password candidates.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** DEBIAN-CVE-2026-42482, GHSA-vrww-7rmp-3xrm, UBUNTU-CVE-2026-42482

## What is CVE-2026-42482?

CVE-2026-42482 is a high-severity memory corruption vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack-based buffer overflow in mangle_to_hex_lower() and mangle_to_hex_upper() in src/rp_cpu.c in hashcat v7.1.2 allows an attacker to cause a denial of service or possibly execute arbitrary code via a crafted rule file, or via the -j or -k rule options used with password candidates of 128 or more characters. The vulnerability is caused by a bounds check that fails to account for the 2x expansion that occurs when password bytes are converted to hexadecimal.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Hashcat Hashcat.

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

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

## Is CVE-2026-42482 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-42484](https://insights.sbomify.com/CVE-2026-42484/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-42483](https://insights.sbomify.com/CVE-2026-42483/): Memory corruption in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42482 is a high-severity memory corruption vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42482 in the wild and no public exploit code.

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

## Sources

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

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