Update dependency koa to v2.16.4 [SECURITY] #32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/npm-koa-vulnerability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.13.0→2.16.4Inefficient Regular Expression Complexity in koa
CVE-2025-25200 / GHSA-593f-38f6-jp5m
More information
Details
Summary
Koa uses an evil regex to parse the
X-Forwarded-ProtoandX-Forwarded-HostHTTP headers. This can be exploited to carry out a Denial-of-Service attack.PoC
Coming soon.
Impact
This is a Regex Denial-of-Service attack and causes memory exhaustion. The regex should be improved and empty values should not be allowed.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Koajs vulnerable to Cross-Site Scripting (XSS) at ctx.redirect() function
CVE-2025-32379 / GHSA-x2rg-q646-7m2v
More information
Details
Summary
In koa < 2.16.1 and < 3.0.0-alpha.5, passing untrusted user input to ctx.redirect() even after sanitizing it, may execute javascript code on the user who use the app.
Patches
This issue is patched in 2.16.1 and 3.0.0-alpha.5.
PoC
Coming soon...
Impact
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Koa Open Redirect via Referrer Header (User-Controlled)
CVE-2025-8129 / GHSA-jgmv-j7ww-jx2x
More information
Details
Summary
In the latest version of Koa, the back method used for redirect operations adopts an insecure implementation, which uses the user-controllable referrer header as the redirect target.
Details
on the API document https://www.koajs.net/api/response#responseredirecturl-alt, we can see:
response.redirect(url, [alt])
however, the "back" method is insecure:
Referrer Header is User-Controlled.
PoC
there is a demo for POC:
Proof Of Concept
Impact
https://learn.snyk.io/lesson/open-redirect/
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:PReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Koa has Host Header Injection via ctx.hostname
CVE-2026-27959 / GHSA-7gcc-r8m5-44qm
More information
Details
Summary
Koa's
ctx.hostnameAPI 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.hostnamereturnsevil.com- an attacker-controlled value. Applications usingctx.hostnamefor 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:The
hostgetter retrieves the raw header value with HTTP/2 and proxy support: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:
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:
Koa parses this as:
ctx.get('Host')"evil.com:fake@legitimate.com:3000"ctx.hostname"evil.com"ctx.host"evil.com:fake@legitimate.com:3000"ctx.origin"http://evil.com:fake@legitimate.com:3000"The
ctx.hostnameAPI returnsevil.combecause the parser splits on the first:without understanding thatevil.com:fake@legitimate.comis a malformed authority component whereevil.com:fakewould be interpreted as userinfo by a proper URI parser.Additional Concern:
ctx.originKoa's
ctx.originproperty concatenates protocol and host without validation:Applications using
ctx.originfor 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 >= 2to read the:authoritypseudo-header:The same vulnerability applies - malformed
:authorityvalues containing userinfo would be accepted and parsed identically.PoC
Setup
Exploit
Result
The password reset URL points to
evil.cominstead of the legitimate server. In a real attack:ctx.hostname→https://evil.com/reset?token=SECRETAdditional Test Cases
Deployment Consideration
For this attack to succeed in production, the malicious Host header must reach the Koa application. This occurs when:
app.proxy = true) -X-Forwarded-Hostcan be injectedImpact
Vulnerability Type
Attack Scenarios
1. Password Reset Poisoning (High Severity)
2. Email Verification Bypass
3. OAuth/SSO Callback Manipulation
ctx.hostnamefor OAuth redirect URIs4. Web Cache Poisoning
5. Server-Side Request Forgery (SSRF)
ctx.hostnameWho Is Impacted
ctx.hostnameorctx.originfor URL generation without additional validationSeverity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
koajs/koa (koa)
v2.16.4Compare Source
What's Changed
ctx.hostnameby @killagu https://github.com/koajs/koa/security/advisories/GHSA-7gcc-r8m5-44qmv2.16.3Compare Source
What's Changed
Full Changelog: https://github.com/koajs/koa/compare/v2.16.2...v2.16.3
v2.16.2Compare Source
What's Changed
Full Changelog: https://github.com/koajs/koa/compare/v2.16.1...v2.16.2
v2.16.1Compare Source
fix: don't render redirect values in anchor ref
v2.16.0Compare Source
This is a backported release to fix core underlying issue with
HEADrequests when usinghttp2.createSecureServer. See discussion at #1593 and #1547.399cb6bv2.15.4Compare Source
Full Changelog: https://github.com/koajs/koa/compare/2.15.3...2.15.4
Fix: avoid redos on host and protocol getter, see https://github.com/koajs/koa/security/advisories/GHSA-593f-38f6-jp5m
v2.15.3Compare Source
v2.15.2Compare Source
v2.15.1Compare Source
v2.15.0Compare Source
v2.14.2Compare Source
v2.14.1Compare Source
v2.14.0Compare Source
v2.13.4Compare Source
v2.13.3Compare Source
v2.13.2Compare Source
v2.13.1Compare Source
==================
fixes
b5472f4] - fix: make ESM transpiled CommonJS play nice for TS folks, fix #1513 (#1518) (miwnwski <m@iwnw.ski>)68d97d6] - fix: fixed order of vulnerability disclosure addresses (niftylettuce <niftylettuce@gmail.com>)others
b4398f5] - correct verb tense in doc (#1512) (Matan Shavit <71092861+matanshavit@users.noreply.github.com>)39e1a5a] - fixed multiple grammatical errors in docs. (#1497) (Hridayesh Sharma <<vyasriday7@gmail.com>>)aeb5d19] - docs: added niftylettuce@gmail.com to vulnerability disclosure (niftylettuce <niftylettuce@gmail.com>)6e1093b] - docs: remove babel from readme (#1494) (miwnwski <m@iwnw.ski>)38cb591] - docs: update specific for auto response status (AlbertAZ1992 <ziyuximing@163.com>)2224cd9] - docs: remove babel ref. (#1488) (Imed Jaberi <imed_jebari@hotmail.fr>)d51f983] - docs: fix assert example for response (#1489) (Imed Jaberi <imed_jebari@hotmail.fr>)f8b49b8] - chore: fix grammatical and spelling errors in comments and tests (#1490) (Matt Kubej <mkubej@gmail.com>)d1c9263] - deps: update depd >> v2.0.0 (#1482) (imed jaberi <imed_jebari@hotmail.fr>)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.