# CVE-2026-2657: wren-lang wren Error Message wren_compiler.c printError stack-based overflow

> A stack-based buffer overflow in the Wren language compiler allows local attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-6rjp-j8mc-4f57

## What is CVE-2026-2657?

CVE-2026-2657 is a medium-severity memory corruption vulnerability in wren-lang wren, published on 18 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in wren-lang wren up to 0.4.0. This impacts the function printError of the file src/vm/wren_compiler.c of the component Error Message Handler. Such manipulation leads to stack-based buffer overflow. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-2657?

It affects 1 product.


Products: Wren Wren.

## How do I fix CVE-2026-2657?

No fix has been published for CVE-2026-2657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2657 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2657 exists.

## Other vulnerabilities in wren-lang wren

- [CVE-2026-3385](https://insights.sbomify.com/CVE-2026-3385/): wren-lang wren wren_compiler.c resolveLocal recursion (medium 4.8)
- [CVE-2026-3386](https://insights.sbomify.com/CVE-2026-3386/): wren-lang wren wren_compiler.c emitOp out-of-bounds (medium 4.8)
- [CVE-2026-3387](https://insights.sbomify.com/CVE-2026-3387/): wren-lang wren wren_compiler.c getByteCountForArguments null pointer dereference (medium 4.8)
- [CVE-2026-2858](https://insights.sbomify.com/CVE-2026-2858/): wren-lang wren Source File wren_compiler.c peekChar out-of-bounds (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2657 and fix it if it is affected.

What it is: CVE-2026-2657 is a medium-severity memory corruption vulnerability in wren-lang wren, published on 18 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2657 exists.

Affected product: wren-lang wren. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2657/ (Markdown: https://insights.sbomify.com/CVE-2026-2657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2657
- OSV: https://osv.dev/vulnerability/CVE-2026-2657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2657/
Summaries are generated and may contain mistakes; the official description above is the record.