CVE-2026-73071 vim CVE debrief

Who should care

System administrators, security teams, and developers using or managing systems with Vim versions 9.2.0511 to 9.2.0844 should assess exposure and prioritize remediation. This includes reviewing system inventories, updating to version 9.2.0844 or later, and monitoring for potential exploitation attempts. Security teams should verify inventory and implement compensating controls where necessary.

Why it matters

CVE-2026-73071 is a low-severity vulnerability in Vim that can cause potential crashes or information disclosure. System administrators and security teams should assess exposure, prioritize remediation, and verify inventory for affected systems.

• Potential crashes or information disclosure due to reading freed memory.
• Local exploitation requires specific conditions and access.
• Remediation priority is low, but recommended to prevent potential issues.
• Verification of exposure and remediation is necessary for affected systems.

Technical summary

The json_decode_item() function in Vim's src/json.c can retain a stale pointer after json_decode_string() invokes channel_fill() to refill and free the current buffer. This can cause the error path to read freed memory instead of reader->js_buf + reader->js_used when an invalid JSON string spans buffers. The issue arises from improper handling of JSON decoding across buffer refills, leading to potential crashes or information disclosure in specific scenarios. Affected versions are from 9.2.0511 to 9.2.0844, fixed in 9.2.0844.

Defensive priority

Low-priority remediation recommended, as exploitation requires local access and specific conditions.

Recommended defensive actions

• Assess exposure: Review systems and deployments using Vim versions 9.2.0511 to 9.2.0844.
• Verify inventory: Check for and update to Vim version 9.2.0844 or later.
• Monitor for exploitation attempts: Implement logging and monitoring to detect potential attacks.
• Remediate vulnerable systems: Prioritize updates for systems with elevated risk profiles.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability is confirmed in Vim versions 9.2.0511 to 9.2.0844. The issue is fixed in version 9.2.0844. The CVE Program and NVD provide official records and assessments. Evidence is limited to public sources and may not reflect all affected systems or potential impacts. Defenders should verify exposure and apply remediation based on official guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.