CVE-2026-102992

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-90364 (ENISA EUVD) · GHSA-67c8-pqhq-4rmx (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

piscina is a node.js worker pool implementation. Prior to 4.9.4, 5.3.2, and 6.0.0-rc.5, Piscina stores ThreadPool.options in src/index.ts as a plain object that inherits from Object.prototype. Applications with a separate prototype-pollution primitive can therefore supply inherited values for security-sensitive options that do not have own defaults. An inherited execArgv value is passed to the Node.js Worker constructor and can preload attacker-controlled code in worker threads, an inherited loadBalancer function can execute during task scheduling, and inherited env values can alter worker environments. This issue is fixed in versions 4.9.4, 5.3.2, and 6.0.0-rc.5.

CVSS
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 30, 2026

Last Modified

September 30, 2026

Advisory Details (8)

Auto-updated Sep 30, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

v6.0.0-rc.5

Patch available: piscinajs/piscina v6.0.0-rc.5 (pre-release)

https://github.com/piscinajs/piscina/releases/tag/v6.0.0-rc.5
GitHub release Patch Available

v5.3.2

Patch available: piscinajs/piscina v5.3.2

https://github.com/piscinajs/piscina/releases/tag/v5.3.2
GitHub release Patch Available

v4.9.4

Patch available: piscinajs/piscina v4.9.4

https://github.com/piscinajs/piscina/releases/tag/v4.9.4
GitHub commit

commit bebbda255c29 (piscinajs/piscina)

Fix landed in piscinajs/piscina commit bebbda255c29 — awaiting tagged release

https://github.com/piscinajs/piscina/commit/bebbda255c2981cecddd36b171b94be2fd41c9a6
GitHub commit Patch Available

commit 5be7bbb19e37 (piscinajs/piscina)

Patch available: piscinajs/piscina v6.0.0-rc.5 (contains commit 5be7bbb19e37)

https://github.com/piscinajs/piscina/commit/5be7bbb19e3787bb698862cd516121a578d690f7
GitHub commit Patch Available

commit 2f69f67159a0 (piscinajs/piscina)

Patch available: piscinajs/piscina v5.3.2 (contains commit 2f69f67159a0)

https://github.com/piscinajs/piscina/commit/2f69f67159a0e48b38fd61fa4a91c2fdc19fff72
GitHub commit Patch Available

commit 0cb12fca37f5 (piscinajs/piscina)

Patch available: piscinajs/piscina v4.9.4 (contains commit 0cb12fca37f5)

https://github.com/piscinajs/piscina/commit/0cb12fca37f526065b072592afe954574dcc656f
GitHub advisoryMentions a patch (unverified)

Prototype-pollution gadget in ThreadPool.options allows RCE via execArgv / loadBalancer / env · Advisory · piscinajs/piscina · GitHub

https://github.com/piscinajs/piscina/security/advisories/GHSA-67c8-pqhq-4rmx

Vendor Advisories for CVE-2026-102992(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmpiscina @ 5.3.2 (fixes >= 5.0.0, < 5.3.2)—ghsa
npmpiscina @ 4.9.4 (fixes < 4.9.4)—ghsa
npmpiscina @ 6.0.0-rc.5 (fixes >= 6.0.0-rc.1, < 6.0.0-rc.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
piscina—
  • 5.0.0 up to 5.3.2: fixed in 5.3.2
  • every version up to 4.9.4: fixed in 4.9.4
  • 6.0.0-rc.1 up to 6.0.0-rc.5: fixed in 6.0.0-rc.5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 185 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 85 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-13 02:58 UTCEchelonGraph re-scored
  3. 2026-11-13 02:58 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-12 02:43 UTCEchelonGraph re-scored
  6. 2026-11-12 02:43 UTCVendor advisory
  7. 2026-11-12 02:43 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  8. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-11-11 02:28 UTCVendor advisory
  10. 2026-11-11 02:28 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  11. 2026-11-10 20:10 UTCEchelonGraph re-scored
  12. 2026-11-10 20:10 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  13. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-09 19:52 UTCEchelonGraph re-scored
  15. 2026-11-09 19:52 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  16. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-11-08 19:37 UTCEchelonGraph re-scored
  18. 2026-11-08 19:37 UTCVendor advisory
  19. 2026-11-08 19:37 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  20. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-11-07 19:22 UTCEchelonGraph re-scored
  22. 2026-11-07 19:22 UTCVendor advisory
  23. 2026-11-07 19:22 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  24. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-11-06 19:07 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-06 19:07 UTCVendor advisory
  2. 2026-11-06 19:07 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  3. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-05 21:55 UTCOSV refresh
  5. 2026-11-05 18:50 UTCEchelonGraph re-scored
  6. 2026-11-05 18:50 UTCVendor advisory
  7. 2026-11-05 18:50 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-11-04 18:35 UTCEchelonGraph re-scored
  10. 2026-11-04 18:35 UTCVendor advisory
  11. 2026-11-04 18:35 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-11-03 18:20 UTCEchelonGraph re-scored
  14. 2026-11-03 18:20 UTCVendor advisory
  15. 2026-11-03 18:20 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  16. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-11-03 14:53 UTCEchelonGraph re-scored
  18. 2026-11-03 14:53 UTCVendor advisory
  19. 2026-11-03 14:53 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  20. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-11-02 14:29 UTCEchelonGraph re-scored
  22. 2026-11-02 14:29 UTCVendor advisory
  23. 2026-11-02 14:29 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  24. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-11-01 14:14 UTCVendor advisory
  26. 2026-11-01 14:14 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  27. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-67c8-pqhq-4rmx · GitHub severity CRITICAL
  28. 2026-11-01 08:00 UTCEchelonGraph re-scored
  29. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-31 13:59 UTCEchelonGraph re-scored
  31. 2026-10-31 13:59 UTCVendor advisory
  32. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-10-30 13:45 UTCEchelonGraph re-scored
  34. 2026-10-30 13:45 UTCVendor advisory
  35. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-29 13:19 UTCEchelonGraph re-scored
  37. 2026-10-29 13:19 UTCVendor advisory
  38. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-10-28 13:02 UTCEchelonGraph re-scored
  40. 2026-10-28 13:02 UTCVendor advisory
  41. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-10-27 12:47 UTCEchelonGraph re-scored
  43. 2026-10-27 12:47 UTCVendor advisory
  44. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  45. 2026-10-26 13:15 UTCEchelonGraph re-scored
  46. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  47. 2026-10-25 14:56 UTCEchelonGraph re-scored
  48. 2026-10-25 12:49 UTCEchelonGraph re-scored
  49. 2026-10-25 12:49 UTCVendor advisory
  50. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  51. 2026-10-24 12:31 UTCEchelonGraph re-scored
  52. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  53. 2026-10-23 12:14 UTCEchelonGraph re-scored
  54. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  55. 2026-10-22 11:56 UTCEchelonGraph re-scored
  56. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  57. 2026-10-21 11:40 UTCEchelonGraph re-scored
  58. 2026-10-21 11:40 UTCVendor advisory
  59. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  60. 2026-10-20 11:26 UTCEchelonGraph re-scored
  61. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  62. 2026-10-19 12:14 UTCEchelonGraph re-scored
  63. 2026-10-19 12:14 UTCVendor advisory
  64. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  65. 2026-10-18 10:24 UTCVendor advisory
  66. 2026-10-18 05:10 UTCEchelonGraph re-scored
  67. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  68. 2026-10-17 08:24 UTCEchelonGraph re-scored
  69. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  70. 2026-10-16 08:08 UTCEchelonGraph re-scored
  71. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  72. 2026-10-15 07:09 UTCEchelonGraph re-scored
  73. 2026-10-15 07:09 UTCVendor advisory
  74. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  75. 2026-10-14 03:03 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-102992?
CVE-2026-102992 is a critical-severity vulnerability; its CVE record was published on September 30, 2026. piscina is a node.js worker pool implementation. Prior to 4.9.4, 5.3.2, and 6.0.0-rc.5, Piscina stores ThreadPool.options in src/index.ts as a plain object that inherits from Object.prototype. Applications with a separate prototype-pollution primitive can therefore supply inherited values for…
When was the CVE record for CVE-2026-102992 published?
The CVE record for CVE-2026-102992 was published on September 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-102992 actively exploited?
CVE-2026-102992 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102992?
CVE-2026-102992 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102992?
A fix for CVE-2026-102992 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102992 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102992

Explore →

Is Your Infrastructure Affected by CVE-2026-102992?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.