dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-26262

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in the component /internals/functions of R-fx Networks Linux Malware Detect v1.6.5 allows attackers to escalate privileges and execute arbitrary code via supplying a file that contains a crafted filename.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in the /internals/functions component of R-fx Networks Linux Malware Detect v1.6.5 allows local attackers to escalate privileges and execute arbitrary code by supplying files with crafted filenames. The vulnerability stems from insufficient input validation of filenames during processing in the affected component.

MitigationUpgrade to a patched version of Linux Malware Detect if available, or implement strict input validation and sanitization for filenames processed by the /internals/functions component to prevent path traversal and code injection via crafted filenames.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Linux Malware Detect installation and version
    Run 'maldet --version' or check for /usr/local/maldet or /opt/maldet directories. Also check 'rpm -q lmd' or 'dpkg -l | grep maldet' if installed via package manager.
    Affected if The installed version is 1.6.5 (or a version you cannot confirm is patched)
  2. Confirm the /internals/functions component exists
    Locate the LMD installation directory and verify the presence of 'internals/functions' or similar files such as 'internals/functions.scan' or 'internals/functions.clam'. Common paths: /usr/local/maldet/internals/ or /var/www/html/maldet/internals/.
    Affected if The internals/functions component exists and is part of the installation
  3. Check file permissions on the LMD internals directory
    Run 'ls -la' on the internals directory to verify permissions. For web-based access, check if the directory is web-accessible.
    Affected if The directory has weak permissions allowing untrusted users to write files, or the web server user can write to processed file directories
  4. Identify directories processed by LMD for malware scanning
    Review LMD configuration files (maldet.conf) for 'scan_paths', 'quarantine_path', or 'sigul_path' directives to find directories LMD monitors and processes.
    Affected if LMD is configured to scan user-writable directories (such as /tmp, /var/tmp, or user home directories) where untrusted files may be placed
  5. Audit recent file creations with unusual filenames
    Use 'find /var/ -newer /usr/local/maldet/maldet 2>/dev/null' or review audit logs/watch folders for files with names containing path traversal sequences (..), special characters, or shell metacharacters in scanned paths.
    Affected if Files with crafted filenames matching patterns used in exploitation (path traversal, code injection sequences) are present in scanned directories

You are affected if Linux Malware Detect v1.6.5 is installed, the internals/functions component processes files from directories with weak permissions, and untrusted users can introduce files with crafted filenames into scanned locations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Linux Malware Detect if available, or implement strict input validation and sanitization for filenames processed by the /internals/functions component to prevent path traversal and code injection via crafted filenames.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26262 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data