vsftpd through 3.0.5 require_ssl_reuse Bypass via FTPS Data Channel Hijacking
Affects vsftpd through 3.0.5 builds compiled with VSF_BUILD_SSL and running ssl_enable=YES in standalone listen mode. No fixed version is listed in the checked facts.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
vsftpd through 3.0.5 contains an authentication bypass vulnerability in ssl_data_accept() that allows unauthenticated attackers to hijack FTPS data connections by resuming their own TLS session ticket. Attackers sharing the victim's source IP can obtain a ticket via AUTH TLS, then connect to the victim's PASV port to steal downloads or inject upload data.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- vsftpd vsftpd
through 3.0.5
References 3
abraxaslabs.tech
security.appspot.com
Questions about CVE-2026-119568
What does this mean?
An attacker who shares the victim's source IP can obtain a ticket via AUTH TLS and use it to hijack other users' FTPS data connections. This can let the attacker steal downloaded files or inject data into uploads.Source: abraxaslabs.tech, vulncheck.com
Am I affected, and how do I check?
The affected range is vsftpd from the first release through 3.0.5. The bug needs a build with SSL compiled in (VSF_BUILD_SSL), which is common in distro builds but not enabled in the stock tarball, plus ssl_enable=YES and standalone listen=YES with require_ssl_reuse=YES (its default). Check the vsftpd version, whether the build has SSL support, and those settings in the configuration file.Source: abraxaslabs.tech, vulncheck.com
What should I do about it?
The checked facts do not list a fixed version, so no upgrade target can be named from them. Follow your distribution's security advisories for a patched package.Source: abraxaslabs.tech, vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts do not give a workaround. The bug depends on ssl_enable=YES in standalone listen mode, so limiting or disabling that FTPS setup is the only option the facts point to, and they do not confirm that it removes the risk.Source: abraxaslabs.tech, vulncheck.com