CVE-2026-44291

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% 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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: 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 used plain objects with inherited prototypes for internal type lookup tables used by generated encode and decode functions. If Object.prototype had already been polluted, those lookup tables could resolve attacker-controlled inherited properties as valid protobuf type information. This could cause attacker-controlled strings to be emitted into generated JavaScript code. This vulnerability is fixed in 7.5.6 and 8.0.2.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

May 13, 2026

Last Modified

May 14, 2026

Advisory Details (1)

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

Code generation gadget after prototype pollution · Advisory · protobufjs/protobuf.js · GitHub

https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-75px-5xx7-5xc7

Vendor Advisories for CVE-2026-44291(3)

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
redhatcryostat/cryostat-grafana-dashboard-rhel9:4.2.0-132026-07-29redhat
redhatansible-automation-platform/automation-portal:17846229512026-07-21redhat

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 6× in last 7d / 64× 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 159 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44291?
CVE-2026-44291 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 used plain objects with inherited prototypes for internal type lookup tables used by generated encode and decode functions. If Object.prototype had already been polluted, those lookup…
When was CVE-2026-44291 disclosed?
CVE-2026-44291 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44291 actively exploited?
CVE-2026-44291 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44291?
CVE-2026-44291 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-44291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44291, 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-44291

Explore →

Is Your Infrastructure Affected by CVE-2026-44291?

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

Start Free Scan →Browse All CVEs