Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2023-50728 @octokit/webhooks

MEDIUM

CVE-2023-50728 is a medium-severity (CVSS 5.4) 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

Also known asGHSA-pwfr-8pq7-x9qv
Published
Dec 15, 2023
Updated
Aug 12, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

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

CVE-2023-50728 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

7 pkgs 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.

137other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@octokit/webhooksnpm
4.4Mdownloads / week

Description

octokit/webhooks is a GitHub webhook events toolset for Node.js. Starting in 9.26.0 and prior to 9.26.3, 10.9.2, 11.1.2, and 12.0.4, there is a problem caused by an issue with error handling in the @octokit/webhooks library because the error can be undefined in some cases. The resulting request was found to cause an uncaught exception that ends the nodejs process. The bug is fixed in octokit/webhooks.js 9.26.3, 10.9.2, 11.1.2, and 12.0.4, app.js 14.02, octokit.js 3.1.2, and Protobot 12.3.3.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
📦npm@octokit/webhooksall versions9.26.3npm install @octokit/webhooks@9.26.3
📦npm@octokit/webhooks10.0.0&&< 10.9.210.9.2npm install @octokit/webhooks@10.9.2
📦npm@octokit/webhooks11.0.0&&< 11.1.211.1.2npm install @octokit/webhooks@11.1.2
📦npm@octokit/webhooks12.0.0&&< 12.0.312.0.3npm install @octokit/webhooks@12.0.3
📦npm@octokit/app14.0.1&&< 14.0.214.0.2npm install @octokit/app@14.0.2
📦npmoctokitall versions3.1.2npm install octokit@3.1.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update @octokit/webhooks to 9.26.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50728 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-50728 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2023-50728. 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.

Red HatModerate

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…

ProductFixed inAdvisory
RHDH-1.1-RHEL-9rhdh/rhdh-hub-rhel9:1.1-97RHEA-2024:1366

Frequently Asked Questions

octokit/webhooks is a GitHub webhook events toolset for Node.js. Starting in 9.26.0 and prior to 9.26.3, 10.9.2, 11.1.2, and 12.0.4, there is a problem caused by an issue with error handling in the @octokit/webhooks library because the error can be undefined in some cases. The resulting request was found to cause an uncaught exception that ends the nodejs process. The bug is fixed in octokit/webhooks.js 9.26.3, 10.9.2, 11.1.2, and 12.0.4, app.js 14.02, octokit.js 3.1.2, and Protobot 12.3.3.
O3 Security · Impact-Aware SCA

Is CVE-2023-50728 in your dependencies?

O3 Security finds CVE-2023-50728 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.