NVD / CVE Program· CNA mitre

CVE-2023-48184: QuickJS before 7414e5f has a quickjs.h JS_FreeValueRT use-after-free because of incorrect garbage collection of async functions with…

LowCVSS 3.9 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 15/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
Someone on the same network segment can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: quickjs (Debian:13) 2024.01.13-1.

Low priority for now. Upgrade to quickjs (Debian:13) 2024.01.13-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

QuickJS before 7414e5f has a quickjs.h JS_FreeValueRT use-after-free because of incorrect garbage collection of async functions with closures.

Memory safety

Published: Apr 23, 2024
Updated: Jun 17, 2026
EPSS: 0.3% · 28th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 15 / 40 · 3.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
quickjs project	quickjs	cpe:2.3:a:quickjs_project:quickjs

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

quickjs project quickjsbefore 2023-12-27

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:13	quickjs	before 2024.01.13-1	2024.01.13-1

Same product

quickjs project: all records

Other highest-scoring records for the same primary product.

CVE-2025-62491Use-after-free in js_std_promise_rejection_check in QuickJS
35Monitor
CVE-2025-62490Use-after-free in js_print_object in QuickJS
35Monitor
CVE-2025-69654A crafted JavaScript input executed with the QuickJS release 2025-09-13, fixed in commit fcd33c1afa7b3028531f53cd1190a3877454f6b3…
30Monitor

Published before and after this one in the same product

← EarlierCVE-2023-31922May 12, 2023 · QuickJS commit 2788d71 was discovered to contain a stack-overflow via the component js_proxy_isArray at quickjs.c.
30Monitor
← EarlierCVE-2023-48183Apr 23, 2024 · QuickJS before c4cdd61 has a build_for_in_iterator NULL pointer dereference because of an erroneous lexical scope of "this" with eval.
30Monitor
Later →CVE-2025-62492Oct 16, 2025 · Heap out-of-bounds read in js_typed_array_indexOf in QuickJS
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:quickjs	2024.01.13-1 · Debian:13	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
Administrator privileges are required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: low · data or configuration can be modified
Availability: low · the service can be disrupted

Attack vector: Adjacent
Attack complexity: High
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: Low
Availability impact: Low

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:49 PM UTC

For records you follow, these changes also arrive as notifications. →

All records