Skip to main content
VulnerabilityPublished

CVE-2026-3979: quickjs · Use After Free

Affects quickjsSource CVE Database V5

0
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 1% 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:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
quickjs-ngquickjsAffected
  • =0.12.0
  • =0.12.1
Fixed in–
GitHubquickjs-ng/quickjspkg:github/quickjs-ng/quickjsOther threatsAffected
  • =0.12.0
  • =0.12.1
Fixed in–

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

AI-suggested

Organizations should promptly apply the patch identified by commit daab4ad4bae4ef071ed0294618d6244e92def4cd to all affected versions of quickjs-ng quickjs (0.12.0 and 0.12.1). Beyond patching, restrict local access to systems running quickjs to trusted users only and implement strict access controls and monitoring to detect suspicious local activity. Employ memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to reduce exploitation success. Conduct code audits and fuzz testing on applications embedding quickjs to identify similar memory management issues. For environments where patching is delayed, consider isolating or sandboxing applications using quickjs to limit impact. Maintain up-to-date inventories of software dependencies to quickly identify affected components. Finally, educate developers and system administrators about the risks of local vulnerabilities and the importance of timely patching.

Description

A flaw has been found in quickjs-ng quickjs up to 0.12.1. This affects the function js_iterator_concat_return of the file quickjs.c. This manipulation causes use after free. The attack requires local access. The exploit has been published and may be used. Patch name: daab4ad4bae4ef071ed0294618d6244e92def4cd. Applying a patch is the recommended action to fix this issue.

References

Community reviews

Loading reviews…