PatchTheCVECVE-2016-10526: A common setup to deploy to gh-pages on every commit via a CI system is to expose a github token to ENV and to
CVE-2016-10526 is a high-severity flaw (CVSS 8.6) affecting grunt-gh-pages. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A common setup to deploy to gh-pages on every commit via a CI system is to expose a github token to ENV and to use it directly in the auth part of the url. In module versions < 0.9.1 the auth portion of the url is outputted as part of the grunt tasks logging function. If this output is publicly available then the credentials should be considered compromised.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2016-10526?
grunt-gh-pages: upgrade to 0.9.1. Exact commands for each OS are on this page.
Is CVE-2016-10526 being exploited?
CVE-2016-10526 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2016-10526 affect?
CVE-2016-10526 affects grunt-gh-pages. Severity is high (CVSS 8.6). A common setup to deploy to gh-pages on every commit via a CI system is to expose a github token to ENV and to use it directly in the auth part of the url. In module versions < 0.9.1 the auth portion of the url is outputted as part of the g
How urgent is CVE-2016-10526?
Priority 54/100. High severity; Remotely exploitable, no login, no user action