Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2026-58041: A flaw in Node.js node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a cac

Noroxi assessment

Priority: Monitor (action score 21/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: nodejs24 (AlmaLinux:10) 1:24.19.0-1.el10_2; nodejs24-devel (AlmaLinux:10) 1:24.19.0-1.el10_2; nodejs24-docs (AlmaLinux:10) 1:24.19.0-1.el10_2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to nodejs24 (AlmaLinux:10) 1:24.19.0-1.el10_2; nodejs24-devel (AlmaLinux:10) 1:24.19.0-1.el10_2; nodejs24-docs (AlmaLinux:10) 1:24.19.0-1.el10_2 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

A flaw in Node.js node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a cached prepared statement after it has been reset and rebound with new parameters. SQLTagStore resets cached statements using sqlite3_reset() directly, bypassing the iterator invalidation mechanism introduced for StatementSync in recent releases This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.

MediumCVSS 5.3 · v3.0—Proof of concept Fix available
Published
Aug 4, 2026
Updated
Oct 23, 2026
EPSS
0.2% · 21th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · hackerone
5.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

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

Follow CVE-2026-58041

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

Running WordPress? Scan your site free with WP Lens

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.

—

Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Watch new CVEs for node

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • nodejs node

    • 22.23.1 and later · up to and including 22.23.1affected · semver
    • 24.18.0 and later · up to and including 24.18.0affected · semver
    • 26.5.0 and later · up to and including 26.5.0affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10nodejs24before 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-develbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-docsbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-full-i18nbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-libsbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-npmbefore 1:11.17.0-1.24.19.0.1.el10_21:11.17.0-1.24.19.0.1.el10_2
AlmaLinux:8nodejsbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-develbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-docsbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-full-i18nbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-libsbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-nodemonbefore 3.1.14-2.module_el8.10.0+4250+09238ed43.1.14-2.module_el8.10.0+4250+09238ed4
AlmaLinux:8nodejs-packagingbefore 2021.06-6.module_el8.10.0+4086+70facd4a2021.06-6.module_el8.10.0+4086+70facd4a
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-6.module_el8.10.0+4086+70facd4a2021.06-6.module_el8.10.0+4086+70facd4a
AlmaLinux:8npmbefore 1:11.17.0-1.24.19.0.1.module_el8.10.0+4268+8e07aa5a1:11.17.0-1.24.19.0.1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8v8-13.6-develbefore 3:13.6.233.17-1.24.19.0.1.module_el8.10.0+4268+8e07aa5a3:13.6.233.17-1.24.19.0.1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:9nodejsbefore 1:24.19.0-1.module_el9.8.0+301+084fac051:24.19.0-1.module_el9.8.0+301+084fac05
AlmaLinux:9nodejs-develbefore 1:24.19.0-1.module_el9.8.0+301+084fac051:24.19.0-1.module_el9.8.0+301+084fac05
AlmaLinux:9nodejs-docsbefore 1:24.19.0-1.module_el9.8.0+301+084fac051:24.19.0-1.module_el9.8.0+301+084fac05
AlmaLinux:9nodejs-full-i18nbefore 1:24.19.0-1.module_el9.8.0+301+084fac051:24.19.0-1.module_el9.8.0+301+084fac05
AlmaLinux:9nodejs-libsbefore 1:24.19.0-1.module_el9.8.0+301+084fac051:24.19.0-1.module_el9.8.0+301+084fac05
AlmaLinux:9nodejs-nodemonbefore 3.1.14-3.module_el9.8.0+292+f4eaf8b23.1.14-3.module_el9.8.0+292+f4eaf8b2
AlmaLinux:9nodejs-packagingbefore 2021.06-6.module_el9.7.0+209+ecf6523e2021.06-6.module_el9.7.0+209+ecf6523e
AlmaLinux:9nodejs-packaging-bundlerbefore 2021.06-6.module_el9.7.0+209+ecf6523e2021.06-6.module_el9.7.0+209+ecf6523e

+70

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 f
    58Plan
  • CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.
    34Monitor
  • CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-58039Jul 31, 2026 · A flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths.
    13Monitor
  • ← EarlierCVE-2026-56846Aug 4, 2026 · A flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion.
    30Monitor
  • Later →CVE-2026-58042Aug 4, 2026 · A flaw in Node.js can cause dns.resolveAny() Aborts the Node.js Process When a DNS Response Contains More Than 256 A Records.
    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 / packageFixed versionSource
almalinux:nodejs1:24.19.0-1.module_el9.8.0+301+084fac05 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-devel1:24.19.0-1.module_el9.8.0+301+084fac05 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-docs1:24.19.0-1.module_el9.8.0+301+084fac05 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-full-i18n1:24.19.0-1.module_el9.8.0+301+084fac05 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-libs1:24.19.0-1.module_el9.8.0+301+084fac05 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.1.14-3.module_el9.8.0+292+f4eaf8b2 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs241:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-devel1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-docs1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-full-i18n1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-libs1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-npm1:11.17.0-1.24.19.0.1.el10_2 · AlmaLinux:10Package registry (OSV)
alpine:nodejs24.18.1-r0 · Alpine:v3.23Package registry (OSV)
alpine:nodejs-current26.5.1-r0 · Alpine:v3.24Package registry (OSV)
debian:nodejs24.19.0+dfsg+~cs24.13.3-1 · Debian:14Package registry (OSV)
opensuse:nodejs2424.18.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nodejs2626.5.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:nodejs220:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-bin0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-devel0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-docs0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-full-i18n0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-libs0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-npm0:10.9.8-1.22.23.2.2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-npm-bin0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs240:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-bin0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-devel0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-docs0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs260:26.7.0-1.5.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)

+2

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-10-23

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.

  1. Published
  2. First PoC+80 d
  3. TodayNov 8, 2026+96 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-10548180 days apartA flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

nvd-secondary

Attack context

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

ATT&CK techniques

—

Change log

  1. Exploit maturitynone → poc
  2. Fix✗ → ✓

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

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records