# CVE-2023-46246: Integer Overflow in :history command in Vim

> An integer overflow in Vim's history command leads to a use-after-free, potentially allowing code execution or crashes.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2023
- **Updated:** 23 Jun 2026
- **Also known as:** AZL-31702, BELL-CVE-2023-46246, DEBIAN-CVE-2023-46246, ECHO-2fe5-91ae-2460, GHSA-q22m-h7m2-9mgm, MGASA-2023-0314, OESA-2023-1796, UBUNTU-CVE-2023-46246

## What is CVE-2023-46246?

CVE-2023-46246 is a medium-severity use after free vulnerability in Vim Vim, published on 27 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vim is an improved version of the good old UNIX editor Vi. Heap-use-after-free in memory allocated in the function `ga_grow_inner` in in the file `src/alloc.c` at line 748, which is freed in the file `src/ex_docmd.c` in the function `do_cmdline` at line 1010 and then used again in `src/cmdhist.c` at line 759. When using the `:history` command, it's possible that the provided argument overflows the accepted value. Causing an Integer Overflow and potentially later an use-after-free. This vulnerability has been patched in version 9.0.2068.

Weakness: CWE-416 (Use After Free), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-46246?

It affects 1 product.


Products: Vim Vim.

## How do I fix CVE-2023-46246?

Apply the vendor's patch.

## Is CVE-2023-46246 being exploited?

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

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3075](https://insights.sbomify.com/CVE-2008-3075/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46246 and fix it if it is affected.

What it is: CVE-2023-46246 is a medium-severity use after free vulnerability in Vim Vim, published on 27 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46246 in the wild and no public exploit code.

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

## Sources

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

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