CVE-2026-44293

HIGHCVSS 7.18.8▲
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% 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 — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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
7.1
EG Score
8.8(medium)
EPSS
31.4%
KEV
Not listed

Published

May 13, 2026

Last Modified

July 15, 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(8)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
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 13× in last 7d / 55× 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 122 total refreshes for this CVE.

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

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 July 15, 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 31.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44293?
CVE-2026-44293 has a CVSS v3 base score of 7.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
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