CVE-2026-24805
Unknown Unknown - Not Provided
Null Pointer Dereference in LiteIDE libvterm Modules Pre-x

Publication date: 2026-01-27

Last updated on: 2026-01-27

Assigner: Government Technology Agency of Singapore Cyber Security Group (GovTech CSG)

Description
NULL Pointer Dereference vulnerability in visualfc liteide (liteidex/src/3rdparty/libvterm/src modules). This vulnerability is associated with program files screen.C, state.C, vterm.C. This issue affects liteide: before x38.4.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-27
Last Modified
2026-01-27
Generated
2026-05-07
AI Q&A
2026-01-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
liteide liteide to x38.4 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a NULL Pointer Dereference in the libvterm component of the liteide project, which occurs when the system runs out of memory while opening a terminal window. It causes the program to crash due to improper handling of memory allocation failures in certain clone functions originally from the vim project. [1]


How can this vulnerability impact me? :

The vulnerability can cause the liteide application to crash unexpectedly when memory resources are exhausted during terminal initialization. This can lead to denial of service or loss of productivity due to application instability. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a NULL Pointer Dereference in the libvterm component of liteide that causes crashes when the system runs out of memory during terminal window initialization. Detection would involve monitoring for crashes or abnormal termination of liteide processes, especially when opening terminal windows. There are no specific commands provided to detect this vulnerability directly. However, you can check for crashes in liteide logs or use system monitoring tools to observe memory allocation failures related to liteide. [1]


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update liteide to version x38.4 or later where the fix has been applied. The fix involves applying a patch from the Vim project that improves memory allocation error handling in libvterm, preventing crashes when memory is exhausted. Until the update is applied, monitor system memory usage and avoid running liteide in low-memory conditions to reduce the risk of triggering the crash. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart