Vulnerability in gvfs
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2026-84270 has been found in gvfs.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "gvfs UBUNTU-CVE-2026-84270" on the vendor's site.
UBUNTU-CVE-2026-84270 (gvfs)
Attack vector: physical / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in gvfs.
Check the vendor advisory for the affected versions of gvfs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gvfs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'gvfs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gvfsを grep し、稼働しているサービス・バージョンを把握する。 -
2
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| Ubuntu:Pro:16.04:LTSgvfs |
All versions→ Not listed |
Not listed |
| Ubuntu:Pro:18.04:LTSgvfs |
All versions→ Not listed |
Not listed |
| Ubuntu:Pro:20.04:LTSgvfs |
All versions→ Not listed |
Not listed |
| Ubuntu:22.04:LTSgvfs |
< 1.48.2-0ubuntu1.3→ 1.48.2-0ubuntu1.3 |
1.48.2-0ubuntu1.3 |
| Ubuntu:24.04:LTSgvfs |
< 1.54.4-0ubuntu1~24.04.5→ 1.54.4-0ubuntu1~24.04.5 |
1.54.4-0ubuntu1~24.04.5 |
| Ubuntu:26.04:LTSgvfs |
< 1.60.0-1ubuntu0.2→ 1.60.0-1ubuntu0.2 |
1.60.0-1ubuntu0.2 |
Original description The description as published by the source.
A flaw was found in the MTP backend in gvfs. When reading a file from a mounted MTP device, do_read() in gvfsbackendmtp.c trusts the data length returned by the device without limiting it to the original size requested by the client. If a malicious MTP device responds with more bytes than requested, this unrestricted length is passed directly to memcpy(). This causes the operation to read memory outside the intended boundaries. This allows an attacker who plugs in a malicious MTP device to cause a segmentation fault when a file is read and crash the gvfsd-mtp process, resulting in a denial of service.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report gitlab.gnome.org