# CVE-2026-12216: svaarala duktape duk_api_bytecode.c memory corruption

> Local attackers can exploit memory corruption in the Duktape JavaScript engine to potentially 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:L/VI:L/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:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-12216, ECHO-38c0-fc48-c568, GHSA-3p43-j8hp-v57p, UBUNTU-CVE-2026-12216

## What is CVE-2026-12216?

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

### Official description

A weakness has been identified in svaarala duktape up to 2.99.99. This issue affects some unknown processing of the file duk_api_bytecode.c. Executing a manipulation of the argument count_instr can lead to memory corruption. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-12216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12216 is a medium-severity memory corruption vulnerability in svaarala duktape, published on 15 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-12216 exists.

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

## Sources

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

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