OpenClaude MCP OAuth Callback: State Check Bypass via error Param Leads to DoS
CVE-2026-42073GHSA-c73c-x77g-854r
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@gitlawb/openclaude 0.5.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.5.1
- Fixed in
- 0.5.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-c73c-x77g-854r lists affected ranges: npm @gitlawb/openclaude >=0 <0.5.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c73c-x77g-854r lists affected ranges: npm @gitlawb/openclaude >=0 <0.5.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-42073: 0.26% estimated exploitation activity in the next 30 days; percentile 17.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
OAuth State Validation Bypass via error Parameter Causes Local Server DoS in MCP Auth Callback --- Description The OpenClaude MCP authentication flow starts a temporary local HTTP server to handle OAuth callbacks. To prevent CSRF attacks, the server validates a state parameter against an internally stored value. However, due to a logic flaw in the order of conditionals, an attacker can completely bypass this check and force the server to shut down — without knowing the state value at all. The vulnerable code looks like this: When a request arrives with an error query parameter (e.g., ?error=anything), the first condition becomes false because !error evaluates to false. This means the CSRF check is never reached. Execution falls through to the second block, where cleanup() is called — shutting down the local server and terminating the user's active authentication session. The attacker does not need to know the state value. Any request containing an error parameter is enough to trigger…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-c73c-x77g-854r
- Revision 1 · created ·
Published from osv record GHSA-c73c-x77g-854r
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-42073 Advisory: OpenClaude MCP OAuth Callback: State Check Bypass via error Param Leads to DoS IDs: CVE-2026-42073, GHSA-c73c-x77g-854r Record: https://patchnext.com/advisories/cve-2026-42073 (revision 2, source checked 26 Oct 2026, 12:53 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @gitlawb/openclaude 0.5.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @gitlawb/openclaude: affected < 0.5.1; fixed in 0.5.1 ## Suggested inspection (read-only) - `npm ls @gitlawb/openclaude --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @gitlawb/openclaude. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-c73c-x77g-854r (OSV record GHSA-c73c-x77g-854r lists affected ranges: npm @gitlawb/openclaude >=0 <0.5.1 (fixed)) - Verified: https://github.com/advisories/GHSA-c73c-x77g-854r (GitHub-reviewed advisory GHSA-c73c-x77g-854r lists affected ranges: npm @gitlawb/openclaude >=0 <0.5.1) Commands are suggestions: review each one before running it.
Loading voting…