CVE-2026-59877

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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 pull request 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(16)

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-26/gateway-rhel9:17896664722026-09-23redhat
redhatcryostat/cryostat-grafana-dashboard-rhel9:4.2.0-142026-09-16redhat
redhatansible-automation-platform-27/gateway-rhel9:17889185102026-09-14redhat
redhatdevspaces/code-rhel9:17877627932026-09-01redhat
redhatopenshift4/ose-console-rhel9:17875905232026-09-01redhat
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
redhatrhdh/rhdh-hub-rhel9:17854116522026-08-03redhat
redhatopenshift-service-mesh/kiali-rhel9:17848063262026-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 rangeFix by version rangeDependents
protobufjs—
  • 7.5.0 up to 7.6.5: fixed in 7.6.5
  • 8.0.0 up to 8.6.6: fixed in 8.6.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 221 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59877?
CVE-2026-59877 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-59877 published?
The CVE record for CVE-2026-59877 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-59877 actively exploited?
CVE-2026-59877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-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?
A fix for CVE-2026-59877 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59877 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs