CVE-2026-56763

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

Score 4.8 from GitHub Security Advisory published 2026-07-11. a secondary CVSS source baseline 4.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Hono before 4.12.7 allows __proto__ key in parseBody with dot option enabled, permitting specially crafted form field names to create objects with __proto__ properties. When parsed results are merged into regular JavaScript objects using unsafe merge patterns, attackers can exploit this to achieve prototype pollution and modify object behavior.

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

Published

July 11, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 11, 2026
Patch available. Sources: github.
generic

Hono - Prototype Pollution via __proto__ Key in parseBody with dot Option | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hono-prototype-pollution-via-proto-key-in-parsebody-with-dot-option
github Patch Available

__proto__ key allowed in parseBody({ dot: true }) · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-v8w9-8mx6-g223

Vendor Advisories for CVE-2026-56763(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
hono4.12.7

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 85× 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 120 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-56763?
CVE-2026-56763 is a medium vulnerability published on July 11, 2026. Hono before 4.12.7 allows proto key in parseBody with dot option enabled, permitting specially crafted form field names to create objects with proto properties. When parsed results are merged into regular JavaScript objects using unsafe merge patterns, attackers can exploit this to achieve…
When was CVE-2026-56763 disclosed?
CVE-2026-56763 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 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-56763 actively exploited?
CVE-2026-56763 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 80.8% of all scored CVEs.
What is the CVSS score of CVE-2026-56763?
CVE-2026-56763 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-56763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56763, 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-56763

Explore →

Is Your Infrastructure Affected by CVE-2026-56763?

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