CVE-2026-78378

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Ransomlook contains a Redis glob pattern injection vulnerability caused by insufficient neutralization of user-controlled input before it is incorporated into Redis SCAN MATCH patterns.

The /api/health/ endpoint attempted to resolve the supplied name to a known group or market, but when resolution failed it fell back to using the attacker-controlled value directly in a Redis key pattern. An unauthenticated attacker could therefore supply Redis glob metacharacters such as *, ?, [ or ] to broaden the SCAN operation beyond the intended group. For example, requesting /api/health/* could enumerate health information, mirror slugs, and uptime series belonging to all groups and markets, including entities marked as private.

Similar unsafe interpolation was present in /api/crypto/chain/ and in the delete_manual_torrent() function. The latter represents a potentially destructive sink because a crafted infohash containing glob metacharacters could cause the scan to match torrent-health keys belonging to other torrents if attacker-controlled input can reach that function.

The patch removes the unsafe fallback from the health endpoint and introduces glob escaping for user-controlled values before they are incorporated into Redis SCAN MATCH expressions.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 26, 2026

Vendor Advisories for CVE-2026-78378(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 22× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 13:52 UTCEG score recompute
  3. 2026-08-29 13:52 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 14:55 UTCGHSA enrichment
  6. 2026-08-27 15:56 UTCEG score recompute
  7. 2026-08-27 15:56 UTCGHSA enrichment
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 17:00 UTCEG score recompute
  10. 2026-08-26 17:00 UTCGHSA enrichment
  11. 2026-08-26 14:47 UTCEPSS rescore
  12. 2026-08-26 14:16 UTCGHSA enrichment
  13. 2026-08-25 15:20 UTCEG score recompute
  14. 2026-08-25 15:20 UTCGHSA enrichment
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-24 16:25 UTCEG score recompute
  17. 2026-08-24 16:25 UTCGHSA enrichment
  18. 2026-08-24 15:33 UTCEG score recompute
  19. 2026-08-24 15:33 UTCGHSA enrichment
  20. 2026-08-24 14:24 UTCEG score recompute
  21. 2026-08-24 13:43 UTCEG score recompute
  22. 2026-08-24 13:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78378?
CVE-2026-78378 is a medium vulnerability published on August 24, 2026. Ransomlook contains a Redis glob pattern injection vulnerability caused by insufficient neutralization of user-controlled input before it is incorporated into Redis SCAN MATCH patterns. The /api/health/<name> endpoint attempted to resolve the supplied name to a known group or market, but when…
When was CVE-2026-78378 disclosed?
CVE-2026-78378 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78378 actively exploited?
CVE-2026-78378 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.0% of all scored CVEs.
What is the CVSS score of CVE-2026-78378?
CVE-2026-78378 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-78378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78378, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78378?

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