Skip to main content
VulnerabilityPublished

CVE-2026-126210: honojs node-server · Interpretation Conflict

Affects honojs node-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.1.6 or 1.19.18 when convenient.

Data as of 12 Nov 2026, 21:36 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 2.1.6, 1.19.18
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade honojs node-server to 2.1.6 or 1.19.18.

Affected software

ProductAffectedFixed in
honojsnode-serverAffected
  • >=2.0.0 <2.1.6
Fixed in
  • 2.1.6
honojsnode-serverAffected
  • <1.19.18
Fixed in
  • 1.19.18

AI-suggested

Upgrade honojs node-server to version 1.19.18 or later if using the 1.x branch, or to version 2.1.6 or later if using the 2.x branch. These versions contain the fix for this interpretation conflict vulnerability. No other mitigation is required as the issue is resolved in these releases.

Description

A vulnerability in honojs node-server versions prior to 1.19.18 and from 2.0.0 up to 2.1.6 allows an unauthenticated client to bypass certain upstream path-based access controls. This occurs because the server passes a raw request-target containing backslashes to the WHATWG URL parser, which treats backslashes as path separators and normalizes the path differently than upstream components. This mismatch can permit access to routes that upstream components intended to block. The issue is fixed in versions 1.19.18 and 2.1.6.

References

Community reviews

Loading reviews…