Skip to content
Fencer Vulns
high 8.6

CVE-2016-10526 json

grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file

published 2018-05-31 8 y ago modified 2026-06-17 4 mo ago also GHSA-rrj3-qmh8-72pf , EUVD-2019-0342

cvss
8.6
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm grunt-gh-pages 0.10.0
  • grunt-gh-pages_project grunt-gh-pages 0.9.1

Exploit prediction

1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.6 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm grunt-gh-pages
<0.10.0
0.10.0

Affected products

  • HackerOne grunt-gh-pages node module

Classification

Weakness
  • CWE-391 DEPRECATED: Unchecked Error Condition
  • CWE-255 Credentials Management Errors
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.