dbcve.org
CWE-183Weakness · CWE-183

CVE-2026-46391

HIGH · 8.7 CVSS v4.0 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HAX CMS helps manage microsite universe with PHP or NodeJs backends. Starting in version 9.0.1 and prior to version 26.0.0 of @haxtheweb/open-apis, multiple functions conduct substring-only matching to validate hostnames to which basic authorization should be sent. An attacker can append the matched substrings to an attacker-controlled endpoint and capture authentication. Version 26.0.0 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HAX CMS @haxtheweb/open-apis versions 9.0.1 through 25.x contain a hostname validation bypass in multiple functions that perform substring-only matching for basic authorization hostnames. Attackers can append matched substrings to attacker-controlled endpoints to intercept authentication credentials.

MitigationUpgrade @haxtheweb/open-apis to version 26.0.0 or later. If upgrade is not immediately possible, audit all functions performing hostname validation and replace substring matching with exact hostname matching or proper URL host validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of @haxtheweb/open-apis
    Run 'npm list @haxtheweb/open-apis' or check the package.json dependencies for the exact version number
    Affected if The version listed is 9.0.1, 9.0.2, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, 18.x, 19.x, 20.x, 21.x, 22.x, 23.x, 24.x, or 25.x (any version from 9.0.1 through 25.x inclusive)
  2. Verify if basic authorization is configured
    Search configuration files for 'basic', 'authorization', or credential-related settings in your HAX CMS setup; inspect the OpenAPI or API configuration for authentication schemes
    Affected if Basic authorization or any hostname-dependent authentication is enabled in the configuration
  3. Locate hostname validation functions in the codebase
    Search the @haxtheweb/open-apis source code for functions performing hostname or host validation; look for patterns like indexOf, includes, substring, or regex matching used on authorization headers or hostnames
    Affected if The code uses substring matching (such as indexOf !== -1, includes, or partial string comparison) rather than exact hostname comparison or proper URL host validation
  4. Test for credential interception via hostname substring injection
    If basic auth is used, attempt a request with a hostname that contains a legitimate authorized hostname as a substring (e.g., if 'example.com' is authorized, test with 'example.com.evil.com')
    Affected if The request succeeds with authentication when the hostname contains the authorized substring but is not the exact hostname

You are affected if @haxtheweb/open-apis version 9.0.1-25.x is installed AND basic authorization is enabled AND the hostname validation relies on substring matching that could allow attacker-controlled hostnames to pass validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade @haxtheweb/open-apis to version 26.0.0 or later. If upgrade is not immediately possible, audit all functions performing hostname validation and replace substring matching with exact hostname matching or proper URL host validation.

Recommended fix High confidence

@haxtheweb/open-apis version 26.0.0

  1. Identify the project using @haxtheweb/open-apis package
  2. Check current installed version with: npm list @haxtheweb/open-apis or yarn list @haxtheweb/open-apis
  3. Update package.json dependency to ^26.0.0 or the specific version 26.0.0
  4. Run npm install or yarn install to fetch the fixed version
  5. Verify the installed version is 26.0.0: npm list @haxtheweb/open-apis
  6. Test the application functionality to ensure the upgrade does not break existing features
Caveat Version jump from 9.x to 26.x may include breaking changes; review changelog before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46391 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data