CVE-2026-28295 | Gvfs: gvfs ftp backend: information disclosure via untrusted pasv responses

A flaw was found in the FTP GVfs backend. A malicious FTP server can exploit this vulnerability by providing an arbitrary IP address and port in its passive mode (PASV) response. The client unconditionally trusts this information and attempts to connect to the specified endpoint, allowing the malicious server to probe for open ports accessible from the client's network.

Published: 2026-02-26 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-28295 is rated Low Risk (21.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-28295

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-22 0.05% 0.04% -0.01%
2 2026-04-21 0.03% 0.05% +0.02%
3 2026-02-27 0.03%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-28295

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]

Weakness enumeration for CVE-2026-28295

OS Trackers for CVE-2026-28295

vendor priority summary link
debian not yet assigned CVE-2026-28295 not yet assigned priority: Debian including 1 source packages (gvfs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-28295
redhat low https://access.redhat.com/security/cve/CVE-2026-28295
suse medium https://www.suse.com/security/cve/CVE-2026-28295/
ubuntu medium CVE-2026-28295 medium priority: Ubuntu including 1 source packages (gvfs), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): released 4, needs-triage 3. https://ubuntu.com/security/CVE-2026-28295

Affected software / configurations for CVE-2026-28295

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-28295

cvelogic Threat Intelligence