CVE-2026-41242

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 92% 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 weekElevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

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.8(medium)
EPSS
50.6%
KEV
Not listed

Published

April 18, 2026

Last Modified

July 15, 2026

Advisory Details (11)

Auto-updated Jul 16, 2026
Patch available. Sources: github_release, github, redhat, github_commit.
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-41242
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:37275
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:26234
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24977
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:21338
github Patch Available

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-v7.6.1 (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.4.2 (contains commit 535df444ac06)

https://github.com/protobufjs/protobuf.js/commit/535df444ac060243722ac5d672db205e5c531d75
redhat

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(4)

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
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 rangeFixed inDependents
protobufjs—7.5.5—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 41× 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 178 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41242?
CVE-2026-41242 is a critical vulnerability 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 CVE-2026-41242 disclosed?
CVE-2026-41242 was first published in the National Vulnerability Database on April 18, 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-41242 actively exploited?
CVE-2026-41242 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41242, 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-41242

Explore →

Is Your Infrastructure Affected by CVE-2026-41242?

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

Start Free Scan →Browse All CVEs