Hono is a Web application framework that provides support for any JavaScript runtime. In versions 4.12.0 and 4.12.1, when using the AWS Lambda adapter (hono/aws-lambda) behind an Application Load Balancer (ALB), the getConnInfo() function incorrectly selected the first value from the X-Forwarded-For header. Because AWS ALB appends the real client IP address to the end of the X-Forwarded-For header, the first value can be attacker-controlled. This could allow IP-based access control mechanisms (such as the ipRestriction middleware) to be bypassed. Version 4.12.2 patches the issue.
CVE-2026-27700
This high-severity CVE scores 7.5 under NVD CVSS v3. 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
February 25, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/honojs/hono/commit/41adbf56e252c04611f8972364ac0887ae07a4c7
- security-advisories@githubhttps://github.com/honojs/hono/releases/tag/v4.12.2
- security-advisories@githubhttps://github.com/honojs/hono/security/advisories/GHSA-xh87-mx6m-69f3
Weakness Classification(2)
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.
- 2026-07-27 14:06 UTCEG score recompute
- 2026-07-27 13:57 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-27700?
When was CVE-2026-27700 disclosed?
Is CVE-2026-27700 actively exploited?
What is the CVSS score of CVE-2026-27700?
How do I remediate CVE-2026-27700?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-27700
Is Your Infrastructure Affected by CVE-2026-27700?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.