CVE-2025-65831VulnerabilityPublished 10 Dec 2025Updated 11 Dec 2025

CVE-2025-65831: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within the impacted component.
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 10 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-26.

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

AI-suggested

1. Immediately discontinue the use of MD5 for password hashing and migrate to secure, modern algorithms such as bcrypt, Argon2, or PBKDF2, which provide salting and computational difficulty to resist cracking. 2. Implement multi-factor authentication (MFA) to reduce the impact of compromised credentials. 3. Conduct thorough audits of all systems and applications to identify any use of MD5 for password hashing or other security-critical functions. 4. Monitor network traffic for signs of TLS downgrade attacks, especially on mobile device communications, and enforce the use of strong TLS versions and cipher suites. 5. Harden cloud service configurations and apply strict access controls to prevent unauthorized access to password hashes or other sensitive data. 6. Educate users on the importance of strong, unique passwords and consider implementing password complexity and rotation policies. 7. Establish incident response procedures to quickly detect and respond to unauthorized access attempts. 8. Collaborate with software vendors to obtain patches or updates that replace insecure hashing algorithms. 9. Regularly review and update security policies to incorporate best practices for password management and cryptographic standards.

Description

The application uses an insecure hashing algorithm (MD5) to hash passwords. If an attacker obtained a copy of these hashes, either through exploiting cloud services, performing TLS downgrade attacks on the traffic from a mobile device, or through another means, they may be able to crack the hash in a reasonable amount of time and gain unauthorized access to the victim's account.

Impact

For European organizations, this vulnerability poses a substantial risk of unauthorized account access, leading to potential data breaches, fraud, and loss of user trust. Compromised credentials can facilitate lateral movement within networks, privilege escalation, and access to sensitive personal or corporate data. The use of cloud services and mobile devices in Europe is widespread, increasing the attack surface for obtaining MD5 hashes via cloud exploitation or TLS downgrade attacks. Regulatory frameworks such as GDPR impose strict requirements on protecting personal data; a breach resulting from this vulnerability could lead to significant legal and financial penalties. The integrity of authentication systems is undermined, potentially affecting critical services including financial platforms, healthcare systems, and government portals. The absence of known exploits in the wild does not diminish the urgency, as the vulnerability is straightforward to exploit given the weak hashing algorithm. Organizations failing to address this risk may face reputational damage and operational disruptions.

Summary

CVE-2025-65831 identifies a critical security vulnerability stemming from the use of the MD5 hashing algorithm for password storage within an application. MD5 is widely recognized as cryptographically broken and unsuitable for password hashing due to its fast computation speed and vulnerability to collision and preimage attacks. Attackers who gain access to password hashes—whether by exploiting cloud infrastructure vulnerabilities, performing TLS downgrade attacks on mobile device communications, or other attack vectors—can leverage modern hardware and rainbow tables to crack MD5 hashes in a reasonable timeframe. This enables unauthorized access to user accounts, compromising the integrity of authentication mechanisms. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS score of 7.5 (high) reflects the network attack vector, low attack complexity, no privileges required, no user interaction, and a significant impact on integrity, though confidentiality and availability impacts are not directly affected. The lack of affected version specifics suggests the issue is tied to the use of MD5 in password hashing rather than a particular software version. No patches are currently listed, indicating a need for developers and organizations to proactively replace MD5 with secure password hashing algorithms such as bcrypt, Argon2, or PBKDF2, which incorporate salting and computational hardness to resist cracking attempts. Additionally, organizations should monitor for anomalous access patterns and consider multi-factor authentication to mitigate risks from compromised credentials.

CWE-327Use of a Broken or Risky Cryptographic Algorithm (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a broken or risky cryptographic algorithm or protocol.
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
Architecture and Design
Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms.
Architecture and Design
Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.7 (opens in a new tab)
V2.9.3 (opens in a new tab)
V6.2.2 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
Cryptanalysis of Cellular Encryption (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

Description

AI analysisMachine-generated, updated 17 Dec 2025, 23:09 UTC

WeaknessesCWE-327

Technical details

References

Community reviews

Related threats