GHSA-pwfr-8pq7-x9qv — @octokit/webhooks
HIGHGHSA-pwfr-8pq7-x9qv is a high-severity (CVSS 8.2) CWE-755 vulnerability in @octokit/webhooks. A fix is available for @octokit/webhooks — see the affected versions and patch details below.
Unauthenticated Denial of Service in the octokit/webhooks library
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-pwfr-8pq7-x9qv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
@octokit/webhooksnpmDescription
Impact
Versions v9.26.0, v10.9.x), v11.1.x, v12.0.x all contained the code that would throw the error.
Specifically, during a pentest we encountered a bug in the octokit/webhooks library (a dependency of Probot, a framework for building Github Apps). The resulting request was found to cause an uncaught exception that ends the nodejs process.
The problem is caused by an issue with error handling in the @octokit/webhooks library because the error can be undefined in some cases.
Credit goes to @pb82 (for the early analysis) and @rh-tguittet (for discovery).
Patches
Maintenance releases for the Error being thrown by the verify method in octokit/webhooks.js
Maintenance release for the reference for octokit/webhooks.js in app.js
Maintenance release for the reference for octokit/webhooks.js in octokit.js
Maintenance release for the reference for octokit/webhooks.js in Protobot
Workarounds
It is recommend that all users upgrade to the latest version of octokit/webhooks.js or use one of the updated back ported versions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @octokit/webhooks | all versions | 9.26.3npm install @octokit/webhooks@9.26.3 |
| 📦npm | @octokit/webhooks | ≥ 10.0.0&&< 10.9.2 | 10.9.2npm install @octokit/webhooks@10.9.2 |
| 📦npm | @octokit/webhooks | ≥ 11.0.0&&< 11.1.2 | 11.1.2npm install @octokit/webhooks@11.1.2 |
| 📦npm | @octokit/webhooks | ≥ 12.0.0&&< 12.0.3 | 12.0.3npm install @octokit/webhooks@12.0.3 |
| 📦npm | @octokit/app | ≥ 14.0.1&&< 14.0.2 | 14.0.2npm install @octokit/app@14.0.2 |
| 📦npm | octokit | all versions | 3.1.2npm install octokit@3.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @octokit/webhooks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @octokit/webhooks to 9.26.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pwfr-8pq7-x9qv 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pwfr-8pq7-x9qv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-pwfr-8pq7-x9qv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The uncaught exception vulnerability in Octokit webhooks presents a moderate severity issue due to its potential to cause service disruptions and expose applications to unexpected behavior. In technical terms, the absence of proper error handling for undefined errors can lead to unhandled exceptions, ultimately…
| Product | Fixed in | Advisory |
|---|---|---|
| RHDH-1.1-RHEL-9 | rhdh/rhdh-hub-rhel9:1.1-97 | RHEA-2024:1366 |
Frequently Asked Questions
Is GHSA-pwfr-8pq7-x9qv in your dependencies?
O3 Security finds GHSA-pwfr-8pq7-x9qv across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.