CVE-2026-57262

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 6.8; sources differ by 0.0.

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

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

A vulnerability has been identified in LOGO! Soft Comfort (All versions < V9). Affected products use a static, hardcoded AES master key to encrypt project files. This could allow a local attacker to extract the master key from the application files or memory and use it to decrypt project files or remove project passwords entirely without knowing the actual user-defined password.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-57262(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 20× in last 7d / 32× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 14:16 UTCEG score recompute
  3. 2026-08-20 14:16 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 14:14 UTCGHSA enrichment
  6. 2026-08-18 15:17 UTCEG score recompute
  7. 2026-08-18 15:17 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 15:07 UTCEG score recompute
  10. 2026-08-17 15:07 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 16:10 UTCEG score recompute
  13. 2026-08-16 16:10 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 17:13 UTCEG score recompute
  17. 2026-08-15 17:13 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 18:15 UTCEG score recompute
  20. 2026-08-14 18:15 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 19:18 UTCGHSA enrichment
  23. 2026-08-12 20:21 UTCEG score recompute
  24. 2026-08-12 20:21 UTCGHSA enrichment
  25. 2026-08-12 19:47 UTCEG score recompute
Show 7 more
  1. 2026-08-12 19:47 UTCGHSA enrichment
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-12 12:22 UTCEG score recompute
  4. 2026-08-12 12:22 UTCGHSA enrichment
  5. 2026-08-11 13:25 UTCEG score recompute
  6. 2026-08-11 12:37 UTCEG score recompute
  7. 2026-08-11 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57262?
CVE-2026-57262 is a medium vulnerability published on August 11, 2026. A vulnerability has been identified in LOGO! Soft Comfort (All versions < V9). Affected products use a static, hardcoded AES master key to encrypt project files. This could allow a local attacker to extract the master key from the application files or memory and use it to decrypt project files or…
When was CVE-2026-57262 disclosed?
CVE-2026-57262 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57262 actively exploited?
CVE-2026-57262 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-57262?
CVE-2026-57262 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-57262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57262, 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-57262

Explore →

Is Your Infrastructure Affected by CVE-2026-57262?

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