CVE-2023-33863VulnerabilityPublished 7 Jun 2023Updated 3 Nov 2025

CVE-2023-33863: n/a

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 25 Oct 2026, 19:02 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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

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.

Impact

For European organizations, the impact of CVE-2023-33863 could be severe, particularly for those involved in software development, game design, and graphics-intensive applications where RenderDoc is commonly used. Exploitation could lead to full system compromise, data breaches, and disruption of critical development workflows. Confidentiality is at risk as attackers could access sensitive source code or proprietary graphics data. Integrity could be compromised by unauthorized code execution or manipulation of debugging outputs, potentially introducing backdoors or malicious modifications. Availability could be affected if attackers cause crashes or denial-of-service conditions. The vulnerability’s remote exploitability without authentication increases the risk of widespread attacks, especially in environments where RenderDoc is exposed to untrusted networks. European companies relying on RenderDoc for debugging or graphics analysis may face operational disruptions and reputational damage if exploited. Additionally, the vulnerability could be leveraged as a foothold for further lateral movement within corporate networks, amplifying the overall risk.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:51 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats