CVE-2026-44293

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — Patch released this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

May 13, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated May 13, 2026
Patch available. Sources: github.
github Patch Available

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 / EcosystemFixed in / 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 rangeFixed inDependents
protobufjs—8.0.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 98× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 205 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44293?
CVE-2026-44293 is a high vulnerability 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 CVE-2026-44293 disclosed?
CVE-2026-44293 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44293 actively exploited?
CVE-2026-44293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44293, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs