CVE-2026-44293

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (53rd 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
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, protobufjs generated JavaScript for toObject conversion could include an unsafe expression derived from a schema-controlled bytes field default value. A crafted descriptor with a non-string default value for a bytes field could cause attacker-controlled code to be emitted into the generated conversion function. This vulnerability is fixed in 7.5.6 and 8.0.2.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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.

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

May 13, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated May 13, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Code injection through bytes field defaults in generated toObject code · Advisory · protobufjs/protobuf.js · GitHub

https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-66ff-xgx4-vchm

Vendor Advisories for CVE-2026-44293(11)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mod-arch-model-registry-rhel9:17872506172026-08-27redhat
redhatopenshift4/ose-console-rhel9:17870314472026-08-26redhat
redhatopenshift4/ose-console-rhel9:17864868222026-08-19redhat
redhatopenshift4/ose-console-rhel9:17835023382026-07-14redhat
redhatopenshift4/ose-console-rhel9:17836023262026-07-14redhat
redhatrh-podman-desktop-0:1.1.1-1.el10_22026-07-09redhat
redhatansible-automation-platform-26/gateway-rhel9:17827615102026-07-01redhat
redhatautomation-platform-ui-0:2.6.10-1.el9ap2026-07-01redhat
redhatopenshift4/ose-console-rhel9:17822243902026-06-30redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatopenshift-service-mesh/kiali-rhel9:17809974382026-06-15redhat

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—
  • every version up to 7.5.6: fixed in 7.5.6
  • 8.0.0 up to 8.0.2: fixed in 8.0.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 27× 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 250 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 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-44293?
CVE-2026-44293 is a high-severity vulnerability; its CVE record was published on May 13, 2026. protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, protobufjs generated JavaScript for toObject conversion could include an unsafe expression derived from a schema-controlled bytes field default value. A crafted descriptor with a non-string default…
When was the CVE record for CVE-2026-44293 published?
The CVE record for CVE-2026-44293 was published on May 13, 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-44293 actively exploited?
CVE-2026-44293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44293?
CVE-2026-44293 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44293?
A fix for CVE-2026-44293 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44293 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-44293

Explore →

Is Your Infrastructure Affected by CVE-2026-44293?

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

Book a Demo →Browse All CVEs