CVE-2026-4753VulnerabilityPublished 24 Mar 2026

CVE-2026-4753: slajerek RetroDebugger · Out-of-bounds Read

Affects slajerek RetroDebuggerSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.64.72 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.64.72

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: There is no loss of integrity within 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 24 Mar 2026
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

Upgrade slajerek/RetroDebugger and RetroDebugger to 0.64.72.

Affected software

Product	Affected	Fixed in
slajerekRetroDebugger	Affected <0.64.72	Fixed in–
GitHubslajerek/RetroDebugger`pkg:github/slajerek/RetroDebugger`Other threats	Affected <0.64.72	Fixed in 0.64.72
GitHubRetroDebugger`pkg:github/RetroDebugger`Other threats	Affected <0.64.72	Fixed in 0.64.72

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict network access to RetroDebugger instances by implementing firewall rules or network segmentation to limit exposure to trusted users and systems only. 2. Monitor vendor communications closely for official patches or updates addressing CVE-2026-4753 and apply them promptly upon release. 3. Employ runtime application self-protection (RASP) or memory protection tools that can detect and prevent out-of-bounds memory accesses during debugging sessions. 4. Conduct thorough code reviews and static analysis of any custom extensions or scripts used with RetroDebugger to identify potential memory safety issues. 5. Use intrusion detection systems (IDS) and network monitoring to detect anomalous traffic patterns that could indicate exploitation attempts targeting RetroDebugger. 6. Educate developers and security teams about the risks associated with exposing debugging tools on public or untrusted networks. 7. Where possible, isolate debugging environments from production networks to minimize the impact of potential exploitation. 8. Consider alternative debugging tools with a stronger security posture until a patch is available.

Description

Out-of-bounds Read vulnerability in slajerek RetroDebugger.This issue affects RetroDebugger: before v0.64.72.

Impact

The vulnerability poses a significant risk to organizations using slajerek RetroDebugger, particularly in software development and security research environments. The high confidentiality impact means attackers could gain unauthorized access to sensitive memory contents, potentially leaking credentials, cryptographic keys, or proprietary code. The high availability impact could disrupt debugging sessions or development workflows by causing crashes or denial of service, delaying critical software development and testing processes. Since the vulnerability is remotely exploitable without authentication, attackers could scan for exposed RetroDebugger instances and launch attacks at scale. This could lead to broader compromise if RetroDebugger is integrated into continuous integration/continuous deployment (CI/CD) pipelines or used in environments with access to sensitive internal networks. Although no known exploits are currently reported, the critical severity and ease of exploitation suggest that threat actors may develop exploits rapidly. Organizations relying on RetroDebugger should consider the potential for data leakage and operational disruption, especially in sectors where software integrity and confidentiality are paramount, such as finance, defense, and technology.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/slajerek/RetroDebugger/pull/97 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 15:01 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats