VulnerabilityPublished 19 Dec 2025

CVE-2025-66910: turms · CVE-2025-66910 is a

Affects turmsSource CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

6.0Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 19 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
GitHubturms-im/turms`pkg:github/turms-im/turms`Other threats	Affected =0.10.0-SNAPSHOT	Fixed in–

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

AI-suggested

Restrict local system access strictly to trusted administrators and monitor for unauthorized access attempts.
Employ endpoint detection and response (EDR) tools to detect suspicious memory access or debugging activities.
Implement strict privilege separation and minimize the number of users with local administrative rights on servers running Turms.
Use memory protection techniques such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to complicate memory analysis.
Regularly audit and monitor authentication logs for anomalies indicating potential credential compromise.
Engage with Turms Server developers or vendors to request patches or updates that eliminate plaintext password caching.
Consider deploying application-level encryption or secure enclave technologies to protect sensitive data in memory.
Conduct internal security training to raise awareness about the risks of local access and memory extraction techniques.
If possible, isolate Turms Server instances in hardened environments with limited access and network segmentation.
Prepare incident response plans specifically addressing credential theft scenarios.

Description

CVE-2025-66910 is a vulnerability in Turms Server v0.10.0-SNAPSHOT and earlier where administrator passwords are stored in plaintext in memory after successful login. This occurs because the BaseAdminService class caches raw passwords unencrypted within AdminInfo objects to optimize authentication performance. Attackers with local system access can extract these passwords via memory dumps, heap analysis, or debugger attachment, bypassing bcrypt protections. The vulnerability has a CVSS score of 6.0, indicating medium severity, with high impact on confidentiality and integrity but no impact on availability. Exploitation requires local privileges and no user interaction. There are no known exploits in the wild or patches currently available. European organizations using Turms Server should be aware of the risk of credential exposure if attackers gain local access.

Impact

For European organizations, the primary impact of CVE-2025-66910 is the potential compromise of administrator credentials if an attacker gains local access to systems running vulnerable Turms Server versions. This can lead to unauthorized administrative control, data breaches, and further lateral movement within networks. Confidentiality is severely impacted as plaintext passwords can be extracted, and integrity is at risk due to possible unauthorized changes by attackers using stolen credentials. Availability is not directly affected. Organizations in sectors with high-value data or critical infrastructure using Turms Server could face significant operational and reputational damage. The requirement for local access limits remote exploitation but increases risk from insider threats or attackers who have already breached perimeter defenses. Given the lack of patches, the vulnerability poses a persistent risk until addressed. European entities with strict data protection regulations (e.g., GDPR) must consider the legal and compliance implications of credential exposure incidents.

CWE-256Plaintext Storage of a Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores a password in plaintext within resources such as memory or files.
Architecture and Design
Avoid storing passwords in easily accessible locations.
Architecture and Design
Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.7.5 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (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 26 Dec 2025, 15:21 UTC

WeaknessesCWE-256, CWE-532

Technical details

References

Community reviews

Related threats