Cyber Resilience

CVE-2026-39409

Hono ≤ 4.12.11

Published
08 April 2026
Modified
24 July 2026
Patch / advisory
View advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0034 27th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2026-39409 is a medium-severity Incorrect Behavior Order: Validate Before Canonicalize (CWE-180) vulnerability in Hono Hono. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.12, ipRestriction() does not canonicalize IPv4-mapped IPv6 client addresses (e.g. ::ffff:127.0.0.1) before applying IPv4 allow or deny rules. In environments such as Node.js dual-stack, this…

more

can cause IPv4 rules to fail to match, leading to unintended authorization behavior. This vulnerability is fixed in 4.12.12.

CWE(s)
CWE-180

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-48913Same product: Hono Hono
CVE-2024-43787Same product: Hono Hono
CVE-2026-39407Same product: Hono Hono
CVE-2026-39408Same product: Hono Hono
CVE-2024-32869Same product: Hono Hono
CVE-2026-29045Same product: Hono Hono
CVE-2026-24398Same product: Hono Hono
CVE-2026-47674Same product: Hono Hono
CVE-2026-39410Same product: Hono Hono
CVE-2026-56761Same product: Hono Hono

Affected Assets

hono
hono
≤ 4.12.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.8
  • V1.1.1
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

SA-11 requires developer testing and evaluation that can discover validation-order defects after they have been coded.

SI-10 Information Input Validation good match

SI-10 requires validity checks on inputs; when implemented with canonicalization preceding validation it structurally prevents the exact ordering flaw.

SA-8 Security and Privacy Engineering Principles partial match

SA-8 mandates security engineering principles that include correct canonicalization-before-validation ordering for input handling.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require correct validation order after canonicalization to prevent bypasses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect validation-order defects before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and canonicalization order, directly addressing CWE-180.

A.8.26 Application security requirements partial match
prevents

Application security requirements include proper input handling to prevent validation-before-canonicalization flaws.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of ordering errors in input processing.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require canonicalize-then-validate to eliminate CWE-180.

References