CVE-2023-33863: RenderDoc · Integer Overflow or Wraparound
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 1.27 : patch RenderDoc as a priority.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 4.1% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- RenderDoc before 1.27
- Patch
- Available – fixed in 1.27
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Jun 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Immediately monitor for the release of RenderDoc version 1.27 or later and apply the update as soon as it becomes available to address this vulnerability.
- If you cannot patch yet, restrict access to RenderDoc instances by limiting network exposure, ideally isolating debugging environments from untrusted or public networks.
- Implement strict input validation and sanitization on any data processed by RenderDoc, especially if integrated into automated pipelines or CI/CD systems.
- Employ application-layer firewalls or intrusion detection/prevention systems (IDS/IPS) to detect anomalous or malformed inputs targeting RenderDoc.
- Conduct thorough code reviews and static analysis on any custom extensions or scripts interacting with RenderDoc to identify potential exploitation vectors.
- Educate development and security teams about the risks associated with integer overflows and buffer overflows to improve early detection of similar vulnerabilities.
- Maintain comprehensive logging and monitoring of RenderDoc usage to quickly identify suspicious activities or exploitation attempts.
- Consider sandboxing RenderDoc processes to limit the impact of potential exploitation on the host system.
Description
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 an attempt to add 1.
References
- renderdoc.org (opens in a new tab)
- qualys.com/2023/06/06/renderdoc/renderdoc.txt (opens in a new tab)
- seclists.org/fulldisclosure/2023/Jun/2 (opens in a new tab)
- packetstormsecurity.com/files/172804/RenderDoc-1.26-Local-Privilege-Escalation-Remote-Code-Execution.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2023/07/msg00023.html (opens in a new tab)
- security.gentoo.org/glsa/202311-10 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/12/msg00008.html (opens in a new tab)