CVE-2025-67745: MyHoard is a daemon for creating, managing and restoring MySQL backups
CVE-2025-67745 is a high-severity flaw (CVSS 7.1) affecting myhoard. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
MyHoard is a daemon for creating, managing and restoring MySQL backups. Starting in version 1.0.1 and prior to version 1.3.0, in some cases, myhoard logs the whole backup info, including the encryption key. Version 1.3.0 fixes the issue. As a workaround, direct logs into /dev/null.
Why this priority
- High severity
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.1 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 95%) |
| CISA exploited list | No |
| Weakness | CWE-402 |
| Published | 2025-12-18 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-67745?
myhoard: upgrade to 1.3.0. Exact commands for each OS are on this page.
Is CVE-2025-67745 being exploited?
CVE-2025-67745 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-67745 affect?
CVE-2025-67745 affects myhoard. Severity is high (CVSS 7.1). MyHoard is a daemon for creating, managing and restoring MySQL backups. Starting in version 1.0.1 and prior to version 1.3.0, in some cases, myhoard logs the whole backup info, including the encryption key. Version 1.3.0 fixes the issue. As
How urgent is CVE-2025-67745?
Priority 31/100. High severity; On your watchlist