Http request which redirect to another hostname do not strip authorization header in @actions/http-client
Impact
If consumers of the http-client:
- make an http request with an authorization header
- that request leads to a redirect (302) and
- the redirect url redirects to another domain or hostname
The authorization header will get passed to the other domain.
Note that since this library is for actions, the GITHUB_TOKEN that is available in actions is generated and scoped per job with these permissions.
Patches
The problem is fixed in 1.0.8 at npm here. In 1.0.8, the authorization header is stripped before making the redirected request if the hostname is different.
Workarounds
None.
References
https://github.com/actions/http-client/pull/27
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/actions/http-client/issues
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @actions/http-client | < 1.0.8 | 1.0.8 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N- Weakness (CWE)
CWE-200- Platform
- npm
- Package
@actions/http-client- Disclosed
- 29.04.2020
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-9w6v-m7wp-jwg4 - CC BY 4.0
Vulnerability history: @actions/http-client
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.