CVE-2025-67745VulnerabilityPublished 18 Dec 2025

CVE-2025-67745: Aiven-Open myhoard · Resource Leak

Affects Aiven-Open myhoardSource CVE Database V5

Not known to be exploited · CVSS 7.1 High : upgrade to 1.3.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.3.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade aiven-open/myhoard to 1.3.0.

Affected software

Product	Affected	Fixed in
GitHubaiven-open/myhoard`pkg:github/aiven-open/myhoard`Other threats	Affected <1.3.0 >=1.0.1	Fixed in 1.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade MyHoard to version 1.3.0 or later, where the vulnerability is fixed. Until patching is possible, administrators should configure the daemon to redirect logs to /dev/null or an equivalent secure logging sink that prevents sensitive data from being stored on disk. Additionally, organizations should audit existing log files for exposure of encryption keys and rotate any compromised encryption keys used for backups. Access controls on log files should be tightened to restrict unauthorized access. Monitoring for unusual access patterns to backup logs and implementing network segmentation to limit access to backup management systems can reduce risk. Regular security reviews of backup and logging configurations should be conducted to prevent similar issues. Finally, organizations should consider encrypting logs or using secure logging frameworks that avoid storing sensitive information in plaintext.

Description

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.

Impact

For European organizations, the exposure of encryption keys through logs can lead to severe confidentiality breaches, allowing attackers to decrypt MySQL backups and access sensitive data such as personal information, financial records, or intellectual property. This can result in regulatory non-compliance, especially under GDPR, leading to legal penalties and reputational damage. Organizations relying on MyHoard for backup management in sectors like finance, healthcare, and critical infrastructure are particularly at risk. The vulnerability could facilitate lateral movement or data exfiltration if attackers gain access to logs. Although no known exploits exist currently, the ease of exploitation and the sensitive nature of the leaked data make this a significant threat. The impact on data integrity and system availability is minimal, but the confidentiality compromise alone warrants urgent remediation.

Summary

CVE-2025-67745 is a vulnerability classified under CWE-402 (Transmission of Private Resources into a New Sphere, or resource leak) affecting the MyHoard daemon developed by Aiven-Open. MyHoard is used to create, manage, and restore MySQL backups. In versions from 1.0.1 up to but not including 1.3.0, the daemon improperly logs detailed backup information, including the encryption keys used to secure the backups. This logging behavior results in sensitive cryptographic material being written to log files, which can be accessed by unauthorized users if log files are improperly secured or exposed. The vulnerability can be exploited remotely over the network with low privileges and does not require user interaction, increasing the risk of automated or stealthy attacks. The impact is primarily on confidentiality, as exposure of encryption keys can lead to unauthorized decryption of backup data, potentially compromising sensitive organizational information. Integrity impact is low since the vulnerability does not directly allow data modification, and availability is not affected. The issue was addressed in MyHoard version 1.3.0 by removing the logging of sensitive information. As an interim mitigation, administrators are advised to redirect logs to /dev/null to prevent sensitive data from being written to disk. No known exploits are reported in the wild as of the publication date. The CVSS v3.1 base score is 7.1, reflecting a high severity due to network attack vector, low attack complexity, and high confidentiality impact.

CWE-402Transmission of Private Resources into a New Sphere ('Resource Leak') (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Dec 2025, 19:11 UTC

WeaknessesCWE-402

Technical details

References

Community reviews

Related threats