Security readout for executives and security teams
Plain-English summary
CVE-2026-1144 is a use-after-free flaw in quickjs-ng QuickJS Atomics handling through version 0.11.0. If an application exposes this JavaScript engine to remote or untrusted input, an attacker may affect confidentiality, integrity, and availability. Public proof-of-concept exploit information is reported, but the provided sources do not show confirmed active exploitation.
Executive priority
Prioritize remediation for products or services that run untrusted JavaScript, especially remote or customer-facing environments. The public exploit signal raises urgency, but the absence of confirmed active exploitation supports a controlled high-priority patch cycle rather than emergency assumptions across unrelated systems.
Technical view
The vulnerability affects quickjs-ng quickjs versions 0.1 through 0.11.0 in quickjs.c, Atomics Ops Handler. VulDB describes remote attack capability and maps the issue to CWE-416 and CWE-119. CVSS v2 is 7.5 with network access, low complexity, and no authentication. The referenced fix is commit ea3e9d77454e8fc9cb3ef3c504e9c16af5a80141.
Likely exposure
Exposure is most likely where quickjs-ng QuickJS is embedded in applications, services, sandboxes, automation, or products that execute JavaScript from users, tenants, plugins, or remote sources. Systems not using quickjs-ng, or not running untrusted JavaScript, are less likely exposed based on the supplied evidence.
Exploitation context
The source bundle states the exploit is public and may be used, and references a GitHub issue tagged as exploit. CISA KEV status is false in the bundle, and no cited source confirms active exploitation in the wild. Treat internet-facing or multi-tenant JavaScript execution paths as higher priority.
Researcher notes
Evidence is largely from VulDB and upstream GitHub references. The vulnerable function is not named beyond quickjs.c Atomics Ops Handler. The bundle identifies affected versions through 0.11.0 and a specific fixing commit, but does not provide a named fixed release. Avoid assuming broader QuickJS variants are affected without confirmation.
Mitigation direction
- Identify all direct and embedded quickjs-ng QuickJS usage.
- Apply vendor fix commit ea3e9d77454e8fc9cb3ef3c504e9c16af5a80141 where applicable.
- Check upstream quickjs-ng guidance for a release containing the fix.
- Restrict untrusted JavaScript execution until patched.
- Prioritize services reachable remotely or used by multiple tenants.
Validation and detection
- Inventory quickjs-ng versions and confirm none are 0.11.0 or earlier.
- Review build manifests, SBOMs, vendored source, and static dependencies.
- Confirm quickjs.c includes the referenced patch changes.
- Check whether Atomics features are enabled in exposed JavaScript contexts.
- Monitor vendor issue and pull request threads for updated remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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 lookupCWE-416: 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-1144 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
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:OF/RC:C
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
1 official scoreWe 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.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:OF/RC:C106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:OF/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341737 | quickjs-ng quickjs Atomics Ops quickjs.c use after freeCVE reference · vdb-entry, technical-description
- VDB-341737 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #735537 | quickjs-ng quickjs v0.11.0 Use After FreeCVE reference · third-party-advisory
- Submit #735538 | quickjs-ng quickjs v0.11.0 Use After Free (Duplicate)CVE reference · third-party-advisory
- https://github.com/quickjs-ng/quickjs/issues/1301CVE reference · issue-tracking
- https://github.com/quickjs-ng/quickjs/pull/1303CVE reference · issue-tracking
- https://github.com/quickjs-ng/quickjs/issues/1302CVE reference · exploit, issue-tracking
- https://github.com/quickjs-ng/quickjs/commit/ea3e9d77454e8fc9cb3ef3c504e9c16af5a80141CVE reference · patch
- https://github.com/quickjs-ng/quickjs/CVE reference · product
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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.