CVE-2016-10526

Description

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.

Severity
HIGH
CVSS v3
8.6
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N · source nvd
Exploit chance (EPSS)
1.581%
chance of exploitation in the next 30 days
higher than 76% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2018-05-31Published by the CNA20:00 UTC
  2. 2019-02-18GitHub advisory published (GHSA-rrj3-qmh8-72pf)263 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-rrj3-qmh8-72pf, affected packages:

PackageVulnerable versionsFixed in
npm grunt-gh-pagesbefore 0.10.00.10.0

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
grunt-gh-pages_project grunt-gh-pagesbefore 0.9.1fixed in 0.9.10.9.1

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources