How severe is GHSA-rrj3-qmh8-72pf?

No CVSS score has been assigned to GHSA-rrj3-qmh8-72pf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rrj3-qmh8-72pf?

GHSA-rrj3-qmh8-72pf affects the following packages: grunt-gh-pages (npm). Ecosystems affected: npm.

How do I fix GHSA-rrj3-qmh8-72pf?

Update grunt-gh-pages to 0.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrj3-qmh8-72pf is resolved across your whole dependency graph.

How do I detect GHSA-rrj3-qmh8-72pf in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grunt-gh-pages, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rrj3-qmh8-72pf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-rrj3-qmh8-72pf actively exploited in the wild?

No public exploit code has been indexed for GHSA-rrj3-qmh8-72pf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rrj3-qmh8-72pf?

GHSA-rrj3-qmh8-72pf has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rrj3-qmh8-72pf?

GHSA-rrj3-qmh8-72pf is classified as CWE-391 (CWE-391), CWE-255 (CWE-255), CWE-532 (CWE-532). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rrj3-qmh8-72pf published, and has it been updated?

GHSA-rrj3-qmh8-72pf was published on February 18, 2019 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log fileGHSA-rrj3-qmh8-72pf

Fix: tschaub/grunt-gh-pages#41

GHSA-rrj3-qmh8-72pf is a CWE-391 vulnerability in grunt-gh-pages. A fix is available for grunt-gh-pages — see the affected versions and patch details below.

Also known asCVE-2016-10526

Published

Feb 18, 2019

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk-0.03%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

grunt-gh-pagesnpm

6Kdownloads / week

Description

Versions of grunt-gh-pages prior to 0.10.0 are affected by a vulnerability which may cause unencrypted GitHub credentials to be written to a log file in certain circumstances.

In the grunt-gh-pages deployment scenario where authentication is performed by injecting a GitHub token directly into the auth portion of the URL, grunt-gh-pages will write the token to a log file, unencrypted.

Recommendation

Update to version 0.10.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`grunt-gh-pages`	all versions	0.10.0`npm install grunt-gh-pages@0.10.0`

Affected Products

1 product · 1 configurations

Application

grunt-gh-pagesgrunt-gh-pages_project

< 0.9.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grunt-gh-pages, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update grunt-gh-pages to 0.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrj3-qmh8-72pf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `grunt-gh-pages` prior to 0.10.0 are affected by a vulnerability which may cause unencrypted GitHub credentials to be written to a log file in certain circumstances. In the `grunt-gh-pages` deployment scenario where authentication is performed by injecting a GitHub token directly into the auth portion of the URL, `grunt-gh-pages` will write the token to a log file, unencrypted. ## Recommendation Update to version 0.10.0 or later.