RenderDoc is a graphics debugging and profiling tool that allows developers to inspect and analyze rendering operations in graphics applications; its narrow product scope centers on the standalone debugger itself. The observed vulnerability exposure reflects the tool's role in low-level graphics API interaction and memory manipulation, with recurring weaknesses in integer overflow and link-resolution logic that are characteristic of systems-level debugging and file-handling code. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Renderdoc over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-33864CRITICAL StreamReader::ReadFromExternal in RenderDoc before 1.27 allows an Integer Overflow with a resultant Buffer Overflow. It uses uint32_t(m_BufferSize-m_InputSize) even though m_InputS | Jun 7, 2023 | 9.8 | 32 | NO | NO |
CVE-2023-33863CRITICAL SerialiseValue in RenderDoc before 1.27 allows an Integer Overflow with a resultant Buffer Overflow. 0xffffffff is sign-extended to 0xffffffffffffffff (SIZE_MAX) and then there is | Jun 7, 2023 | 9.8 | 31 | NO | NO |
CVE-2023-33865HIGH RenderDoc before 1.27 allows local privilege escalation via a symlink attack. It relies on the /tmp/RenderDoc directory regardless of ownership. | Jun 7, 2023 | 7.8 | 25 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Renderdoc.
Media articles that mention a CVE ID that affects a product developed by Renderdoc — matched by CVE ID, not by vendor name.