CVE-2026-41242

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.0% (61st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
9.8EG
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: 1.0%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

protobufjs compiles protobuf definitions into JavaScript (JS) functions. In versions prior to 8.0.1 and 7.5.5, attackers can inject arbitrary code in the "type" fields of protobuf definitions, which will then execute during object decoding using that definition. Versions 8.0.1 and 7.5.5 patch the issue.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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
1.0%
EPSS %ILE
61st
KEV
Not listed

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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

April 18, 2026

Last Modified

September 9, 2026

Advisory Details (12)

Auto-updated Oct 15, 2026
Patch available. Sources: github_commit, github_release, github, redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:62260
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:37275
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:26234
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:24977
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:21338
GitHub advisoryMentions a patch (unverified)

Code execution through attacker-controlled protobuf definitions · Advisory · protobufjs/protobuf.js · GitHub

https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-xq3m-2v4x-88gg
GitHub release Patch Available

protobufjs: v8.0.1

Patch available: protobufjs/protobuf.js protobufjs-v8.0.1

https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.0.1
GitHub release Patch Available

v7.5.5

Patch available: protobufjs/protobuf.js protobufjs-v7.5.5

https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.5.5
GitHub commit Patch Available

commit ff7b2afef875 (protobufjs/protobuf.js)

Patch available: protobufjs/protobuf.js protobufjs-cli-v1.3.3 (contains commit ff7b2afef875)

https://github.com/protobufjs/protobuf.js/commit/ff7b2afef8754837cc6dc64c864cd111ab477956
GitHub commit Patch Available

commit 535df444ac06 (protobufjs/protobuf.js)

Patch available: protobufjs/protobuf.js protobufjs-cli-v2.5.1 (contains commit 535df444ac06)

https://github.com/protobufjs/protobuf.js/commit/535df444ac060243722ac5d672db205e5c531d75
Red HatMentions a patch (unverified)

CVE-2026-41242 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-41242
Red Hat

2459442 – (CVE-2026-41242) CVE-2026-41242 protobufjs: protobufjs: Arbitrary code execution via injected protobuf definition type fields

https://bugzilla.redhat.com/show_bug.cgi?id=2459442

Vendor Advisories for CVE-2026-41242(6)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatdevspaces/code-rhel9:17877627932026-09-01redhat
redhatrhoai/odh-mod-arch-maas-rhel9:17830826802026-07-09redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatrhdh/rhdh-hub-rhel9:17798415862026-05-27redhat

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
protobufjs—
  • 8.0.0 up to 8.0.1: fixed in 8.0.1
  • every version up to 7.5.5: fixed in 7.5.5
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 36× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 295 refreshes 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 195 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41242?
CVE-2026-41242 is a critical-severity vulnerability; its CVE record was published on April 18, 2026. protobufjs compiles protobuf definitions into JavaScript (JS) functions. In versions prior to 8.0.1 and 7.5.5, attackers can inject arbitrary code in the "type" fields of protobuf definitions, which will then execute during object decoding using that definition. Versions 8.0.1 and 7.5.5 patch the…
When was the CVE record for CVE-2026-41242 published?
The CVE record for CVE-2026-41242 was published on April 18, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-41242 actively exploited?
CVE-2026-41242 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41242?
CVE-2026-41242 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41242?
A fix for CVE-2026-41242 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41242 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-41242

Explore →

Is Your Infrastructure Affected by CVE-2026-41242?

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

Book a Demo →Browse All CVEs