CWE-913Weakness · CWE-913

CVE-2026-48700

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-22

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

98/100

Remediation priority · Urgent

No privileges Zero-click

Official description

NVD · unedited

An issue was discovered in all versions of PCManFM-Qt starting from 1.1.0. When a regular file's path is passed as a URI in an org.freedesktop.FileManager1.ShowFolders D-Bus method call, PCManFM-Qt delegates to a different program (based on the file type) without user confirmation. This could be used to achieve code execution or circumvent network namespace restrictions. NOTE: those outcomes are potentially unwanted by most users; however, the behavior of the product does comply with the applicable specification, and a simplistic solution (ensuring that the URI does not name a regular file) may have adverse consequences for I/O.

Technical summary

dbcve analysis · moderate confidence

PCManFM-Qt's implementation of the org.freedesktop.FileManager1.ShowFolders D-Bus method accepts URIs pointing to regular files and automatically delegates to external programs based on file type without user confirmation, leading to arbitrary code execution or bypass of network namespace restrictions.

MitigationImplement validation to ensure URIs passed to ShowFolders point to directories, or add user confirmation dialogs before delegating to external programs, while carefully testing to avoid breaking legitimate file I/O operations.

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

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
Authentication: None
User interaction: None
Scope: X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:I/V:D/RE:M/U:Clear

Am I affected?

dbcve checks

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

Identify PCManFM-Qt version

Run 'pcmanfm-qt --version' or check your package manager for the installed pcmanfm-qt package version

Affected if Version is 1.1.0 or higher
Verify D-Bus service is running

Run 'dbus-send --session --dest=org.freedesktop.FileManager1 --type=method_call --print-reply /org/freedesktop/FileManager1 org.freedesktop.FileManager1.Interfaces' to check if the FileManager1 interface is available

Affected if The D-Bus service responds and lists the org.freedesktop.FileManager1 interface
Confirm ShowFolders method accepts regular files

Inspect the D-Bus introspection data: run 'dbus-send --session --dest=org.freedesktop.FileManager1 --type=method_call --print-reply /org/freedesktop/FileManager1 org.freedesktop.DBus.Introspectable.Introspect' and check if ShowFolders method exists in the interface

Affected if ShowFolders method exists and the implementation does not filter out regular file paths (this requires code review or testing with a benign file path)
Check for user confirmation behavior

Test the ShowFolders method with a regular file path using dbus-send and observe whether a confirmation dialog appears before external program execution

Affected if No user confirmation dialog appears and the file is automatically processed by an external program based on file type

You are affected if PCManFM-Qt version 1.1.0 or higher is installed AND the D-Bus org.freedesktop.FileManager1 service is running AND the ShowFolders method processes regular files without prompting for user confirmation.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement validation to ensure URIs passed to ShowFolders point to directories, or add user confirmation dialogs before delegating to external programs, while carefully testing to avoid breaking legitimate file I/O operations.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation12.0 h
Testing6.0 h
Review / QA3.0 h

25.0 hours of engineering $4,400

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-48700 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-48700?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 9.3 Critical

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 25 hrs · Moderate

Typical engagement from $4,400

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-48700 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References