High 8.8

Vulnerability in gvfs

CVE-2026-84268 First seen on SecPulse Sep 2, 01:17

AI summary

Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.

A vulnerability tracked as CVE-2026-84268 has been found in gvfs.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "gvfs CVE-2026-84268" on the vendor's site.

CVE-2026-84268 (gvfs) — CWE-122 / CVSS v3 8.8
Attack vector: remote (network-reachable) / 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.

What is the problem

A vulnerability (CWE-122) exists in gvfs.

Affected scope

Check the vendor advisory for the affected versions of gvfs.

Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

How to fix

Update to the patched release per vendor advisory.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

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

Ecosystem	Package	Affected → Fixed	Fixed
GNOME	GNOMEgvfs	< 1.60.2→ 1.60.2	1.60.2
Red Hat	Red HatRed Hat Enterprise Linux 10	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 10.0 Extended Update Support	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 7 Extended Lifecycle Support	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8.8 Telecommunications Update Service	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 8.8 Update Services for SAP Solutions	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 9	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 9.2 Update Services for SAP Solutions	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 9.4 Update Services for SAP Solutions	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 9.6 Extended Update Support	—	Not listed
Red Hat	Red HatRed Hat Enterprise Linux 6	—	Not listed

Fix status by distribution

Records published by each distribution for this CVE. Fixed versions differ by release; check each link.

Debian DEBIAN-CVE-2026-84268 gvfs Fix available
Ubuntu UBUNTU-CVE-2026-84268 gvfs Fix available

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: NIST National Vulnerability Database NVD GitHub Advisory

AI summary

Response actions

Affected packages

Fix status by distribution

References