On this page (7 sections)
A critical authentication bypass has been published for Ghost, a project by the GitHub user muneeb141 (not to be confused with the better-known Ghost publishing platform; the record describes a repository at github.com/muneeb141/ghost). According to the NVD record for CVE-2026-130070, an unauthenticated attacker can skip one-time-password (OTP) verification and receive OAuth tokens for existing accounts.
If you run code from this repository on its main branch, or built something on top of it, you should treat this as urgent. If you only use the Ghost publishing platform from ghost.org, nothing in the NVD record ties this CVE to it.
What happened
The vulnerable code is a whitelisted method, ghost.api.ghost.convert_to_real_user. Its apparent job is to turn a temporary guest-style session into a real user session after the person proves control of an email address with an OTP. The NVD description says the method accepts a client-supplied bypass_otp parameter, and when the caller sets it, the OTP check is skipped.
The record was published on 2026-11-16. The technical detail in this article comes solely from the NVD description. No independent confirmation or analysis was available to us, so verify finer points, such as exact behavior in your deployment, in your own code.
How the weakness works
The classic mistake here is letting the client decide whether a security check applies. A server should decide when to require an OTP based on its own state. When a request parameter can turn verification off, the check is only a suggestion.
Per the NVD description, the attack chain has two steps and needs no credentials:
- The attacker obtains a ghost session from the create_ghost_session endpoint, which is accessible to guests.
- The attacker calls convert_to_real_user with an arbitrary real_email and bypass_otp set to 1, and receives OAuth tokens for the existing account that matches that email.
The result is account takeover: whoever knows or guesses a registered email address can obtain tokens for that account. Because the email is arbitrary, administrator or high-privilege accounts are the obvious concern, though the record does not say which accounts exist in any given deployment.
Who is affected
The affected range is the main branch of the muneeb141 Ghost repository from commit c731cdf through commit 672dfec. Because this is a branch range rather than a versioned release, the exposure depends on which commit you deployed.
- Teams that cloned or deployed the repository and track main.
- Developers who vendored or forked the code and kept the convert_to_real_user method.
- Agencies or hosts running an app built from this repository for clients.
The record lists no package ecosystem for this CVE, so package-manager audits will probably not flag it. You need to check your own source tree.
How to check your exposure
Start by finding out which commit you run. This read-only command, run inside your checked-out copy of the repository, prints the current commit hash. Compare it with the range c731cdf through 672dfec.
git rev-parse --short HEADTo see whether your commit sits inside the affected range, this read-only command lists the commits in your history. Look for c731cdf and 672dfec in the output.
git log --onelineThen search the code for the vulnerable parameter. This grep shows where bypass_otp is read, so you can see whether client input can influence the OTP check.
grep -rn "bypass_otp" .What to do now
The NVD record does not name a patched release. It does reference two commits in the repository (commit 641db34 and commit 7023a4a), but it does not say whether either one is the fix, so review them yourself before relying on them. The vulnerable file at commit 672dfec and a VulnCheck advisory are also linked from the record; we did not have the advisory's content, so we have not relied on it here.
- Identify every deployment built from the muneeb141 Ghost repository and note its commit.
- If it falls in the range c731cdf to 672dfec, take the app offline or restrict access (IP allowlist, VPN or authentication at the proxy) until it is fixed.
- Review the two referenced commits, then update to code where the OTP check cannot be skipped by request input.
- If you cannot update quickly, remove or disable the convert_to_real_user method from the whitelist, or strip the bypass_otp parameter so the server always enforces OTP.
- Revoke and reissue OAuth tokens and sessions, since tokens may already have been issued to an attacker.
- Force a credential review for privileged accounts and check them for unexpected changes.
- Add a regression test that confirms a request with bypass_otp set still requires a valid OTP.
Detection and monitoring
No exploitation reports were provided and the CVE is not in CISA KEV, but the attack uses normal-looking API calls, so look for the pattern in your own logs. Useful signals include a create_ghost_session call followed closely by a convert_to_real_user call from the same client, requests that include bypass_otp, and OAuth tokens issued to accounts without a matching OTP delivery or verification event.
This read-only search checks an access or application log for the parameter name. Replace the path with your own log location. Any hit is worth investigating, since legitimate clients should have no reason to send it.
grep -n "bypass_otp" /path/to/your/app-or-access.logRequest bodies are often not logged, so an empty result does not prove safety. If you cannot rule out abuse, assume tokens were issued and rotate them. For broader hygiene, see our guides on what to do if a website is hacked and how to check if a website is hacked. A web application firewall can help you filter requests containing unexpected parameters while you patch, though it is not a substitute for fixing the code.
A lesson for custom login code
If you maintain custom login or OTP code, audit it for any request parameter that lets a client influence a security decision, such as skipping a verification step. Verification state should live on the server, and flags like this should not be accepted from the client at all.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
