CVE-2026-59877

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted .proto schema that opens an option declaration and ends prematurely can cause parse, Root.load, or Root.loadSync to loop indefinitely. This issue is fixed in versions 7.6.5 and 8.6.6.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (6)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Denial of Service via infinite loop in .proto option parsing · Advisory · protobufjs/protobuf.js · GitHub

https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-j3f2-48v5-ccww
github_release Patch Available

protobufjs: v8.6.6

Patch available: protobufjs/protobuf.js protobufjs-v8.6.6

https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.6.6
github_release Patch Available

protobufjs: v7.6.5

Patch available: protobufjs/protobuf.js protobufjs-v7.6.5

https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.6.5
github_pr Patch Available

fix: handle EOF during options parsing

Patch available: protobufjs/protobuf.js protobufjs-cli-v2.5.7 (PR #2352 merged 2026-07-03)

https://github.com/protobufjs/protobuf.js/pull/2352
github_commit Patch Available

commit fa5c73add738 (protobufjs/protobuf.js)

Patch available: protobufjs/protobuf.js protobufjs-cli-v2.5.7 (contains commit fa5c73add738)

https://github.com/protobufjs/protobuf.js/commit/fa5c73add738ceb471e74da8cc2f3727c3d0a69f
github_commit Patch Available

commit 10fba6d54815 (protobufjs/protobuf.js)

Patch available: protobufjs/protobuf.js protobufjs-v7.6.5 (contains commit 10fba6d54815)

https://github.com/protobufjs/protobuf.js/commit/10fba6d54815ceecca8a06b9a6db490c8f5d2217

Vendor Advisories for CVE-2026-59877(11)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-console-rhel9:17871583412026-08-25redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatrhdh/rhdh-hub-rhel9:17859728432026-08-10redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17860065732026-08-06redhat
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat
redhatansible-automation-platform/automation-portal:17858573032026-08-05redhat
redhatopenshift-service-mesh/kiali-rhel9:17848063262026-08-03redhat
redhatrhdh/rhdh-hub-rhel9:17854116522026-08-03redhat
redhatopenshift-service-mesh/kiali-rhel9:17848067082026-08-03redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:17853328252026-07-29redhat

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.6.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 115× 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 154 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59877?
CVE-2026-59877 is a high vulnerability published on July 8, 2026. protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted .proto schema that opens an option declaration and ends…
When was CVE-2026-59877 disclosed?
CVE-2026-59877 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59877 actively exploited?
CVE-2026-59877 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 70.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59877?
CVE-2026-59877 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59877?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59877, 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-59877

Explore →

Is Your Infrastructure Affected by CVE-2026-59877?

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

Start Free Scan →Browse All CVEs