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-84268 has been found in gvfs.
Successful exploitation can lead to full system takeover.
What to do: upgrade gvfs to 1.28.2-1ubuntu1~16.04.3+esm1 or later.
If unsure, ask your IT team or search "gvfs UBUNTU-CVE-2026-84268" on the vendor's site.
UBUNTU-CVE-2026-84268 (gvfs)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.28.2-1ubuntu1~16.04.3+esm1 — apply immediately
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: ?. Successful exploitation can lead to full system takeover.
Update to 1.28.2-1ubuntu1~16.04.3+esm1.
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
Apply patchpatch
Upgrade gvfs to 1.28.2-1ubuntu1~16.04.3+esm1ステージング環境で 1.28.2-1ubuntu1~16.04.3+esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| Ubuntu:Pro:16.04:LTSgvfs |
< 1.28.2-1ubuntu1~16.04.3+esm1→ 1.28.2-1ubuntu1~16.04.3+esm1 |
1.28.2-1ubuntu1~16.04.3+esm1 |
| Ubuntu:Pro:18.04:LTSgvfs |
< 1.36.1-0ubuntu1.3.3+esm1→ 1.36.1-0ubuntu1.3.3+esm1 |
1.36.1-0ubuntu1.3.3+esm1 |
| Ubuntu:Pro:20.04:LTSgvfs |
< 1.44.1-1ubuntu1.2+esm1→ 1.44.1-1ubuntu1.2+esm1 |
1.44.1-1ubuntu1.2+esm1 |
| Ubuntu:22.04:LTSgvfs |
< 1.48.2-0ubuntu1.2→ 1.48.2-0ubuntu1.2 |
1.48.2-0ubuntu1.2 |
| Ubuntu:24.04:LTSgvfs |
< 1.54.4-0ubuntu1~24.04.4→ 1.54.4-0ubuntu1~24.04.4 |
1.54.4-0ubuntu1~24.04.4 |
| Ubuntu:26.04:LTSgvfs |
< 1.60.0-1ubuntu0.1→ 1.60.0-1ubuntu0.1 |
1.60.0-1ubuntu0.1 |
Original description The description as published by the source.
A flaw was found in the SFTP backend in gvfs. When mounting a share and reading a file, a malicious SFTP server can cause read_reply() to process a length that exceeds the size requested by the client. The function does not verify the server-provided length against the allocated buffer size, causing the operation to write past the intended boundaries. This issue allows a malicious server to corrupt adjacent heap memory in the gvfsd-sftp process, resulting in a denial of service as the process aborts upon detecting the heap corruption or potentially allowing arbitrary code execution.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report gitlab.gnome.org