CVE-2026-56763

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:vulncheck
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 4.8Exploit: NoneExposed: 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(low)
EPSS
—
KEV
Not listed

Published

July 11, 2026

Last Modified

July 11, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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.

  1. 2026-07-11 13:33 UTCEG score recompute
  2. 2026-07-11 13:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

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. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-56763?
CVE-2026-56763 has a CVSS v3 base score of 4.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs