Cyber Resilience

CVE-2023-2610

Memory Safety in Vim ≤ 9.0.1532

Public PoCMemory Safety
Published
09 May 2023
Modified
23 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0049 39th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-2610 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Vim Vim. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

Integer Overflow or Wraparound in GitHub repository vim/vim prior to 9.0.1532.

CWE(s)
CWE-190

Related Threats

CVEs Like This One

CVE-2023-46246Same product: Vim Vim
CVE-2026-32249Same product: Vim Vim
CVE-2026-28422Same product: Vim Vim
CVE-2026-59857Same product: Vim Vim
CVE-2026-52859Same product: Vim Vim
CVE-2026-55693Same product: Vim Vim
CVE-2026-55892Same product: Vim Vim
CVE-2023-2426Same product: Vim Vim
CVE-2025-9390Same product: Vim Vim
CVE-2026-57451Same product: Vim Vim

Affected Assets

vim
vim
≤ 9.0.1532

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect integer overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

A.8.26 Application security requirements partial match
degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References