What is the CVSS score of CVE-2025-25595?

CVE-2025-25595 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Safe are affected by CVE-2025-25595?

Organizations using the login page of Safe App face critical risk from CVE-2025-25595, a brute-force weakness vulnerability rated CVSS 9.8.

How to fix or mitigate CVE-2025-25595?

Within 24 hours: Identify all affected systems running the login page of Safe App and apply vendor patches immediately. Monitor vendor channels for patch availability.

Safe CVE-2025-25595

CRITICAL

Improper Restriction of Excessive Authentication Attempts (CWE-307)

2025-03-18 cve@mitre.org

Authentication Bypass Safe

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:32 vuln.today

CVE Published

Mar 18, 2025 - 17:15 nvd

CRITICAL 9.8

DescriptionCVE.org

A lack of rate limiting in the login page of Safe App version a3.0.9 allows attackers to bypass authentication via a brute force attack.

AnalysisAI

A lack of rate limiting in the login page of Safe App version a3.0.9 allows attackers to bypass authentication via a brute force attack. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-307. A lack of rate limiting in the login page of Safe App version a3.0.9 allows attackers to bypass authentication via a brute force attack. Affected products include: Iitb Safe.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.