# CVE-2026-10267: janet-lang janet debug.c doframe out-of-bounds

> A local attacker can trigger an out-of-bounds read in the Janet language runtime, potentially causing crashes or leaking memory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-mmcx-pc5f-m5m4

## What is CVE-2026-10267?

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

### Official description

A security flaw has been discovered in janet-lang janet up to 1.41.0. This affects the function doframe of the file src/core/debug.c. Performing a manipulation results in out-of-bounds read. Attacking locally is a requirement. The exploit has been released to the public and may be used for attacks. The patch is named ed17dd2c5913a23fb1107251e44a9410a3c30cf5.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-10267 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10267 is a medium-severity memory corruption vulnerability in janet-lang janet, published on 1 Jun 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-10267 exists.

Affected product: janet-lang janet. 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-10267/ (Markdown: https://insights.sbomify.com/CVE-2026-10267/index.md)
```

## Sources

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

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