Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-25030: A vulnerability classified as problematic has been found in Mirmay Secure Private Browser and File Manager up

21
Routine
LOW 3.3UPGRADEUPGRADE

CVE-2018-25030 is a low-severity flaw (CVSS 3.3) affecting file manager, secure private browser. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as problematic has been found in Mirmay Secure Private Browser and File Manager up to 2.5. Affected is the Auto Lock. A race condition leads to a local authentication bypass. The exploit has been disclosed to the public and may be used.

Why this priority

  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score3.3 (Low)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 81%)
CISA exploited listNo
WeaknessCWE-287, CWE-362
Published2022-03-28
Last modified2026-06-17
Publisher (CNA): VulDB · Vendor: mirmay

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

mirmay file manager UPGRADE
Affected: <= 2.5
Fixed in: newer than 2.5
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy file-manager || rpm -q file-manager || file-manager --version
2. UPGRADE to newer than 2.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade file-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade file-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
mirmay secure private browser UPGRADE
Affected: <= 2.5
Fixed in: newer than 2.5
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy secure-private-browser || rpm -q secure-private-browser || secure-private-browser --version
2. UPGRADE to newer than 2.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade secure-private-browser
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade secure-private-browser
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
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-2018-25030?

file manager: upgrade to newer than 2.5; secure private browser: upgrade to newer than 2.5. Exact commands for each OS are on this page.

Is CVE-2018-25030 being exploited?

CVE-2018-25030 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-2018-25030 affect?

CVE-2018-25030 affects file manager, secure private browser. Severity is low (CVSS 3.3). A vulnerability classified as problematic has been found in Mirmay Secure Private Browser and File Manager up to 2.5. Affected is the Auto Lock. A race condition leads to a local authentication bypass. The exploit has been disclosed to the

How urgent is CVE-2018-25030?

Priority 21/100. Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.