# CVE-2026-119568: vsftpd through 3.0.5 require_ssl_reuse Bypass via FTPS Data Channel Hijacking


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** AZL-111799, DEBIAN-CVE-2026-119568, GHSA-93qj-4wg6-29x9, UBUNTU-CVE-2026-119568

## What is CVE-2026-119568?

CVE-2026-119568 is a critical vulnerability in vsftpd, published on 30 Oct 2026. 

### Official description

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.

Weakness: CWE-940 (Improper Verification of Source of a Communication Channel)

## Which versions are affected by CVE-2026-119568?


## How do I fix CVE-2026-119568?

Upgrade to a fixed version.

## Is CVE-2026-119568 being exploited?

There is no known exploitation of CVE-2026-119568 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119568 and fix it if it is affected.

What it is: CVE-2026-119568 is a critical vulnerability in vsftpd, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119568 in the wild and no public exploit code.

Affected product: vsftpd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119568/ (Markdown: https://insights.sbomify.com/CVE-2026-119568/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119568
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119568
- OSV: https://osv.dev/vulnerability/CVE-2026-119568

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119568/
Summaries are generated and may contain mistakes; the official description above is the record.