CVE-2026-24798
Improper Memory Buffer Restriction in DagorEngine Causes Potential Crash
Publication date: 2026-01-27
Last updated on: 2026-01-27
Assigner: Government Technology Agency of Singapore Cyber Security Group (GovTech CSG)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Affected Vendors & Products
| Vendor | Product | Version |
|---|---|---|
| gaijinentertainment | dagorengine | to dagor_2025_01_15 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GaijinEntertainment's DagorEngine involves improper restriction of operations within the bounds of a memory buffer, specifically in the upnpreplyparse.C file. It is related to improper initialization of a data structure used for SOAP parsing in the ParseNameValue() function, which originated from code cloned from the miniupnp project. This improper initialization can lead to security risks such as buffer overflows or memory corruption. [1]
How can this vulnerability impact me? :
The vulnerability can lead to serious security risks including potential memory corruption or buffer overflow attacks. This can allow an attacker to execute arbitrary code, cause a denial of service, or compromise the affected system's integrity and availability. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, apply the security fix that properly initializes the data structure used in the ParseNameValue() function within the DagorEngine project. This fix eliminates the improper restriction of operations within the bounds of a memory buffer. The patch was merged on April 16, 2025, and is available in the main branch of the DagorEngine repository. Updating to this fixed version will address the vulnerability. [1]