CVE-2026-130070

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-17. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-126723 (ENISA EUVD) · GHSA-r5hh-7566-f3p3 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 17, 2026

Advisory Details (5)

Auto-updated Nov 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

Ghost (muneeb141) Authentication Bypass via bypass_otp in convert_to_real_user | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ghost-muneeb141-authentication-bypass-via-bypass-otp-in-convert-to-real-user
GitHub commit

commit 641db34f6456 (muneeb141/ghost)

Fix landed in muneeb141/ghost commit 641db34f6456 — awaiting tagged release

https://github.com/muneeb141/ghost/commit/641db34f6456c15f381358e2e631df66ea170842
Web page

ghost/ghost/api/ghost.py at 672dfec9346dfd935c87fdc6ded554014a36d7f4 · muneeb141/ghost · GitHub

https://github.com/muneeb141/ghost/blob/672dfec9346dfd935c87fdc6ded554014a36d7f4/ghost/api/ghost.py#L33-L35
Web page

ghost/ghost/api/ghost.py at 672dfec9346dfd935c87fdc6ded554014a36d7f4 · muneeb141/ghost · GitHub

https://github.com/muneeb141/ghost/blob/672dfec9346dfd935c87fdc6ded554014a36d7f4/ghost/api/ghost.py#L182-L190
GitHub commit

commit 7023a4a9275e (muneeb141/ghost)

Fix landed in muneeb141/ghost commit 7023a4a9275e — awaiting tagged release

https://github.com/muneeb141/ghost/commit/7023a4a9275e9f359116337fee40651d0165bc34

Vendor Advisories for CVE-2026-130070(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 03:48 UTCEchelonGraph re-scored
  2. 2026-11-22 03:48 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  4. 2026-11-21 01:32 UTCEchelonGraph re-scored
  5. 2026-11-21 01:32 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  7. 2026-11-19 23:17 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-19 18:58 UTCEchelonGraph re-scored
  9. 2026-11-19 18:58 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  11. 2026-11-18 16:43 UTCEchelonGraph re-scored
  12. 2026-11-18 16:43 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  14. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  15. 2026-11-17 14:28 UTCEchelonGraph re-scored
  16. 2026-11-17 14:28 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-11-17 14:13 UTCEchelonGraph re-scored
  18. 2026-11-17 14:13 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-11-17 00:46 UTCEchelonGraph re-scored
  20. 2026-11-17 00:46 UTCGHSA enrichmentGHSA-r5hh-7566-f3p3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-16 23:02 UTCENISA EUVD ID recordedEUVD-2026-126723 · Source: ENISA EUVD
  22. 2026-11-16 22:30 UTCEchelonGraph re-scored
  23. 2026-11-16 22:10 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
  24. 2026-11-16 22:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130070?
CVE-2026-130070 is a critical-severity vulnerability; its CVE record was published on November 16, 2026. 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…
When was CVE-2026-130070 made public?
CVE-2026-130070 was made public on October 21, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 16, 2026. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-130070 actively exploited?
CVE-2026-130070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130070?
CVE-2026-130070 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130070?
An upstream fix for CVE-2026-130070 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-130070 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-130070

Explore →

Is Your Infrastructure Affected by CVE-2026-130070?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.