Analyst readout for executives and security teams
Plain-English summary
CVE-2026-12216 is a memory corruption issue in Duktape, an embeddable JavaScript engine. It requires local access, so it is not described as remotely exploitable. A public exploit reference exists, but the sources do not show active exploitation. Business urgency is moderate, especially for products or appliances embedding affected Duktape versions.
Executive priority
Handle as a medium-priority exposure review. Prioritize internet-facing platforms only if they also allow local code execution paths. Prioritize multi-user systems, developer workstations, appliances, and products embedding Duktape until vendor remediation guidance is available.
Technical view
The issue affects svaarala Duktape through 2.99.99 in duk_api_bytecode.c. Manipulating the count_instr argument can cause memory corruption, mapped to CWE-119. CVSS 3.1 is 5.3 with local attack vector, low complexity, low privileges, no user interaction, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in software, appliances, or internal tools embedding Duktape 2.99.0 through 2.99.99. Risk is higher where local users can trigger Duktape bytecode handling. The source bundle does not identify downstream affected products or a vendor-supplied fixed version.
Exploitation context
VulDB states the exploit has been made public and could be used for attacks. The issue requires local access and low privileges. CISA KEV status is false in the provided data, and no cited source confirms active exploitation in the wild.
Researcher notes
The public record is limited. VulDB reports vendor contact without response and lists an exploit reference. The affected processing is described as unknown beyond duk_api_bytecode.c and count_instr manipulation. No official patch, commit, or downstream advisory is included in the source bundle.
Mitigation direction
- Inventory products and codebases that embed Duktape.
- Identify Duktape versions 2.99.0 through 2.99.99.
- Check Duktape and product-vendor guidance for fixed releases or workarounds.
- Limit local access to systems running affected Duktape components.
- Avoid enabling Duktape bytecode handling where not required.
Validation and detection
- Confirm whether Duktape is present in application dependencies or firmware.
- Compare detected versions against the affected 2.99.x range.
- Review whether affected deployments use Duktape bytecode APIs.
- Monitor vendor advisories for remediation status.
- Track public CVE and VulDB entries for updates.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-12216 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 1.8 3.4 VulDB CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 1.8 3.4 VulDB 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 — — VulDB AV:L/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 3.1 6.4 VulDB Vulnerability scoring details
Base CVSS 4.0 score
4.8 MediumVector: 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
Base CVSS 3.1 score
5.3 MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
5.3 MediumVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
4.3 MediumVector: AV:L/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 source CVE List V5
- VDB-370859 | svaarala duktape duk_api_bytecode.c memory corruption CVE reference, VulDB · vdb-entry, technical-description
- VDB-370859 | CTI Indicators (IOB, IOC, IOA) CVE reference, VulDB · signature, permissions-required
- CVE-2026-12216 | CVE Analysis and Report CVE reference, VulDB · third-party-advisory
- Submit #833814 | Duktape https://github.com/svaarala/duktape <=2.99.99 Memory Corruption CVE reference, VulDB · third-party-advisory
- https://github.com/hmKunlun/compileOOB/blob/main/api_bytecode.md CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.