VulnerabilityPublished 1 Mar 2026Updated 2 Mar 2026

CVE-2026-3385: wren · Uncontrolled Recursion

Affects wrenSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
wren-langwren	Affected 0.1 – 0.4.0 4 affected builds	Fixed in–
GitHubwren-lang/wren`pkg:github/wren-lang/wren`Other threats	Affected 0.1 – 0.4.0 4 affected builds	Fixed in–

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

AI-suggested

To mitigate CVE-2026-3385, organizations should first identify all instances of wren-lang wren versions 0.1 through 0.4.0 in their environments. 2) Implement strict access controls and monitoring to detect unusual local activity that could indicate exploitation attempts. 3) If feasible, replace or upgrade wren-lang with a version that addresses this vulnerability once released. 4) For embedded systems, consider disabling or sandboxing scripting capabilities that invoke wren to limit exposure. 5) Review and harden development and deployment processes to prevent untrusted code execution within wren environments. 6) Monitor public advisories for updates or patches from the wren-lang project. 7) As a temporary workaround, developers may audit and modify the resolveLocal function to add recursion depth checks or safeguards against infinite recursion if source code access and expertise are available. These targeted mitigations go beyond generic advice by focusing on local access restrictions, code auditing, and environment hardening specific to wren usage.

Description

A vulnerability was detected in wren-lang wren up to 0.4.0. Affected is the function resolveLocal of the file src/vm/wren_compiler.c. The manipulation results in uncontrolled recursion. Attacking locally is a requirement. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-3385 is denial of service through uncontrolled recursion leading to resource exhaustion. Organizations using wren-lang in development environments, embedded systems, or scripting engines may experience application crashes or system instability if an attacker with local access exploits this flaw. While the vulnerability does not allow privilege escalation or remote code execution, disruption of availability can affect development workflows or embedded device functionality. The requirement for local access limits the attack scope, reducing risk in environments with strong access controls. However, insider threats or compromised local accounts could leverage this vulnerability to cause service interruptions. The public availability of an exploit increases the likelihood of opportunistic attacks. Systems that embed wren in critical infrastructure or IoT devices may face operational risks if exploited. Overall, the impact is moderate but could be significant in environments where wren is integral to system operation or automation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Mar 2026, 01:20 UTC

Technical details

References

Community reviews

Related threats