CVE-2026-78553

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). 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 — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.0Exploit: 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.

RansomLook created its Flask session-signing key without explicitly restricting the file permissions. The secret_key file was created using the process's default permissions and umask, resulting in permissions such as 0644 under a common 022 umask. Consequently, other local users able to access the RansomLook home directory could read the application's cryptographic secret.

The exposed key is security-critical because it is used to sign Flask session cookies and is also involved in the legacy API-key key derivation. An attacker who obtains the key can generate valid session cookies and impersonate an authenticated user, including an administrator. In LDAP configurations, exploitation may be particularly straightforward because the session user loader does not require the supplied username to correspond to an existing local user.

Successful exploitation requires local access sufficient to read the improperly protected file, but can result in complete compromise of RansomLook's authentication and authorization controls.

The patch creates new secret-key files atomically with permissions 0600 and also restricts permissions on existing key files during application startup.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity70% × 45%
The EG Score, 7.0 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

Published

August 24, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit df9d47edcf02 (RansomLook/RansomLook)

Fix landed in RansomLook/RansomLook commit df9d47edcf02 — awaiting tagged release

https://github.com/RansomLook/RansomLook/commit/df9d47edcf02dd0125db869d5bc19d93f426d892

Vendor Advisories for CVE-2026-78553(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 103× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 99 of 175 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 76 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-10 12:31 UTCEG score recompute
  3. 2026-10-10 12:31 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-09 04:41 UTCEG score recompute
  6. 2026-10-09 04:41 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-08 03:50 UTCEG score recompute
  9. 2026-10-08 03:50 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-07 01:11 UTCEG score recompute
  12. 2026-10-07 01:11 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-06 13:48 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  15. 2026-10-06 02:47 UTCEG score recompute
  16. 2026-10-06 02:47 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-05 13:49 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  19. 2026-10-05 02:37 UTCEG score recompute
  20. 2026-10-05 02:37 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-04 15:36 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  23. 2026-10-04 04:16 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  24. 2026-10-03 17:15 UTCEG score recompute
  25. 2026-10-03 17:15 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
Show 74 more
  1. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-03 06:12 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  3. 2026-10-02 19:05 UTCEG score recompute
  4. 2026-10-02 19:05 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  5. 2026-10-02 08:02 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  6. 2026-10-01 21:01 UTCEG score recompute
  7. 2026-10-01 21:00 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-01 07:18 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  10. 2026-09-30 20:17 UTCEG score recompute
  11. 2026-09-30 20:17 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  12. 2026-09-30 06:59 UTCEG score recompute
  13. 2026-09-30 06:59 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  14. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-09-29 08:33 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  16. 2026-09-28 21:32 UTCEG score recompute
  17. 2026-09-28 21:32 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  18. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-09-28 07:36 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  20. 2026-09-27 20:35 UTCEG score recompute
  21. 2026-09-27 20:35 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-27 09:34 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  24. 2026-09-26 22:18 UTCEG score recompute
  25. 2026-09-26 22:18 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  26. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  27. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-25 16:56 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  29. 2026-09-25 05:55 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  30. 2026-09-24 18:53 UTCEG score recompute
  31. 2026-09-24 18:53 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  32. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-24 07:36 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  34. 2026-09-23 20:35 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  35. 2026-09-23 09:34 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  36. 2026-09-22 22:33 UTCEG score recompute
  37. 2026-09-22 22:33 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  38. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-09-22 11:31 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  40. 2026-09-22 00:29 UTCEG score recompute
  41. 2026-09-22 00:29 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  42. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-09-21 13:27 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  44. 2026-09-21 02:26 UTCEG score recompute
  45. 2026-09-21 02:26 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  46. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-09-20 15:25 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  48. 2026-09-20 04:19 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  49. 2026-09-19 17:18 UTCEG score recompute
  50. 2026-09-19 17:18 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  51. 2026-09-19 06:17 UTCEG score recompute
  52. 2026-09-19 06:17 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  53. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-09-18 19:15 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  55. 2026-09-18 08:13 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  56. 2026-09-17 21:11 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  57. 2026-09-17 09:52 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  58. 2026-09-16 22:51 UTCEG score recompute
  59. 2026-09-16 22:51 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  60. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-09-16 11:48 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  62. 2026-09-16 00:47 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  63. 2026-09-15 13:36 UTCEG score recompute
  64. 2026-09-15 13:36 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  65. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-09-15 02:31 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  67. 2026-09-14 15:25 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  68. 2026-09-14 04:19 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  69. 2026-09-13 17:18 UTCEG score recompute
  70. 2026-09-13 17:18 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  71. 2026-09-13 06:16 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  72. 2026-09-12 19:15 UTCEG score recompute
  73. 2026-09-12 19:15 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH
  74. 2026-09-12 08:14 UTCGHSA enrichmentGHSA-5453-gcx7-h56m · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-78553?
CVE-2026-78553 is a high vulnerability published on August 24, 2026. RansomLook created its Flask session-signing key without explicitly restricting the file permissions. The secret_key file was created using the process's default permissions and umask, resulting in permissions such as 0644 under a common 022 umask. Consequently, other local users able to access the…
When was the CVE record for CVE-2026-78553 published?
The CVE record for CVE-2026-78553 was published on August 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 26, 2026; the record at its source may have been updated since.
Is CVE-2026-78553 actively exploited?
CVE-2026-78553 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78553?
CVE-2026-78553 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78553?
An upstream fix for CVE-2026-78553 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-78553 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78553?

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