CVE-2026-84269
CVE-2026-84269 — Gvfs: afp: heap-based buffer overflow in dsi read path
A flaw was found in the AFP backend in gvfs. When mounting a share, a malicious AFP server can cause the DSI read path to process a length that exceeds the size requested by the client. The function does not verify the server-provided length against the pre-sized reply buffer, causing the operation to access past the intended boundaries. This issue allows a malicious server to overflow a heap buffer and crash the gvfsd-afp process, resulting in a denial of service.
Published Updated Sources: NVD, Red Hat (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX), SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
6.5
medium
Remediation
The vendor's own words where we have them.
Upgrade Red Hat Enterprise Linux 10 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
Red Hat VEX · CVE-2026-84269
workaround: To mitigate this vulnerability, do not connect to untrusted AFP servers.
no_fix_planned: Out of support scope
none_available: Fix deferred
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Red Hat | Red Hat Enterprise Linux 10 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 6 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 7 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 8 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 9 | — | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
None
Integrity
None
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | medium | 2.8 | 3.6 | NVD, Red Hat (CNA), GHSA, Red Hat (VEX) |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-122 · Heap-based Buffer Overflow
- DoS: Crash, Exit, or Restart
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
- Execute Unauthorized Code or Commands
Mitigation: Pre-design: Use a language or compiler that performs automatic bounds checking.
Weakness & attack patterns
- CWE-122Heap-based Buffer Overflow
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
1
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 6.5 (AV:N)
Sep 1, 2026 · NVD
Initial · CVE published
Sep 1, 2026 · NVD
Reported to Red Hat.
Sep 1, 2026 · Red Hat
Added · GHSA-7jmj-69v2-2vjf published (medium)
Sep 1, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 1, 2026 · SOCRadar CTI
Reported · Made public.
Aug 3, 2026 · Red Hat
References
6 on the record
- access.redhat.com/security/cve/CVE-2026-84269
Vendor Advisory, NIST
- bugzilla.redhat.com/show_bug.cgi?id=2526784
Vendor Advisory, Mitre, NIST
- gitlab.gnome.org/GNOME/gvfs/-/issues/863
Vendor Advisory, NIST
- nvd.nist.gov/vuln/detail/CVE-2026-84269
NVD
- github.com/advisories/GHSA-7jmj-69v2-2vjf
Exploit, Third Party Advisory
- www.cve.org/CVERecord?id=CVE-2026-84269
Vendor Advisory
Elsewhere on this site
- Red Hatevery CVE for this vendor
- Memory Corruptionsame class
- CWE-122other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-84269 is Gvfs: afp: heap-based buffer overflow in dsi read path, a medium vulnerability affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 from Red Hat. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-84269. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.