Skip to main content
VulnerabilityPublished Updated

CVE-2023-33863: RenderDoc · Integer Overflow or Wraparound

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 1.27 : patch RenderDoc as a priority.

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jun 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

  1. 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.
  2. If you cannot patch yet, restrict access to RenderDoc instances by limiting network exposure, ideally isolating debugging environments from untrusted or public networks.
  3. Implement strict input validation and sanitization on any data processed by RenderDoc, especially if integrated into automated pipelines or CI/CD systems.
  4. Employ application-layer firewalls or intrusion detection/prevention systems (IDS/IPS) to detect anomalous or malformed inputs targeting RenderDoc.
  5. Conduct thorough code reviews and static analysis on any custom extensions or scripts interacting with RenderDoc to identify potential exploitation vectors.
  6. Educate development and security teams about the risks associated with integer overflows and buffer overflows to improve early detection of similar vulnerabilities.
  7. Maintain comprehensive logging and monitoring of RenderDoc usage to quickly identify suspicious activities or exploitation attempts.
  8. 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

Community reviews

Loading reviews…