CVE Tools

CVE-2025-11837

Malware Remover

No known exploitation. EPSS puts it in the 73rd percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check your installed Malware Remover version and confirm whether it is earlier than 6.6.8.20251023.
  2. If you are on an earlier version, upgrade Malware Remover to 6.6.8.20251023 or later.
  3. If you cannot upgrade right away, isolate the affected system from the internet and any untrusted networks until the upgrade is completed.
  4. After upgrading, verify the Malware Remover service is running normally and re-check the installed version to ensure the update actually took effect.

What it is

From the CVE record

An improper control of generation of code vulnerability has been reported to affect Malware Remover. The remote attackers can then exploit the vulnerability to bypass protection mechanism. We have already fixed the vulnerability in the following version: Malware Remover 6.6.8.20251023 and later

In plain language

Written by AI from the record

CVE-2025-11837 is a serious remote code execution flaw in Malware Remover that attackers are actively exploiting in the wild; if you use Malware Remover and are not on the fixed version, you should act immediately.

CVE-2025-11837 is a remotely exploitable code-generation/control weakness (CWE-94) in Malware Remover that allows unauthenticated attackers to execute arbitrary code or bypass protections; exploitation is confirmed in the wild via the AryStinger campaign targeting legacy routers.

If you're affected

  • Full device compromise
  • Malware and botnet enrollment
  • Network scanning and proxying
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS73rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.5% chance of exploitation activity in the next 30 days, which ranks it in the 73rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 20 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

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

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Malware Remover, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store