CVE
Ghost authentication bypass in OTP verification
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in < 641db34f6456c15f381358e2e631df66ea170842
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: < 641db34f6456c15f381358e2e631df66ea170842.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Ghost by muneeb141 contains an authentication bypass that lets an unauthenticated attacker skip OTP verification by setting a client-supplied parameter. Reachable remotely over the network without logging in, the flaw lets an attacker receive OAuth tokens for existing accounts and take those accounts over.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Ghost by muneeb141 on the main branch from commit c731cdf through commit 672dfec contains an authentication bypass vulnerability in the whitelisted ghost.api.ghost.convert_to_real_user method that allows unauthenticated attackers to skip OTP verification by setting the client-supplied bypass_otp parameter. Attackers can obtain a ghost session from the guest-accessible create_ghost_session endpoint, then call convert_to_real_user with an arbitrary real_email and bypass_otp=1 to receive OAuth tokens for existing accounts and take them over.
Who should check
Teams running muneeb141 ghost from the main branch between commit c731cdf and commit 672dfec, including anyone using create_ghost_session and convert_to_real_user.
“Ghost by muneeb141 on the main branch from commit c731cdf through commit 672dfec”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: < 641db34f6456c15f381358e2e631df66ea170842.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130070 (Ghost (muneeb141) Authentication Bypass via bypass_otp in convert_to_real_user), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130070 (entry last updated 2026-11-16):
Affected:
- muneeb141 ghost: version range not reported
Fixed versions: < 641db34f6456c15f381358e2e631df66ea170842.
Conditions (all must be true for the bug to be hit):
- Ghost by muneeb141 on the main branch from commit c731cdf through commit 672dfec (source: https://www.vulncheck.com/advisories/ghost-muneeb141-authentication-bypass-via-bypass-otp-in-convert-to-real-user)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130070 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130070 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/muneeb141/ghost/commit/7023a4a9275e9f359116337fee40651d0165bc34
- https://github.com/muneeb141/ghost/commit/641db34f6456c15f381358e2e631df66ea170842
- https://github.com/muneeb141/ghost/blob/672dfec9346dfd935c87fdc6ded554014a36d7f4/ghost/api/ghost.py#L182-L190
- https://github.com/muneeb141/ghost/blob/672dfec9346dfd935c87fdc6ded554014a36d7f4/ghost/api/ghost.py#L33-L35
- https://www.vulncheck.com/advisories/ghost-muneeb141-authentication-bypass-via-bypass-otp-in-convert-to-real-user
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130070
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130070"}.Timeline
- CVE published
- First seen by cve.now1 day
- Posted on X by cve.now
Affected versions
- muneeb141 ghost
Version range not reported
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130070
Is CVE-2026-130070 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bypass_otp path in convert_to_real_user lets an attacker skip OTP verification. The attacker can then receive OAuth tokens for existing accounts and take them over.Source: vulncheck.com
Am I affected, and how do I check?
Ghost by muneeb141 on the main branch from commit c731cdf through commit 672dfec is affected. To check a copy, compare its commit against that range.Source: vulncheck.com
How do I fix CVE-2026-130070?
Update to commit 641db34f6456c15f381358e2e631df66ea170842 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com