# CVE-2025-14242: Vsftpd: vsftpd: denial of service via integer overflow in ls command parameter parsing > A remote authenticated attacker can cause a denial of service in vsftpd via an integer overflow in the STAT command parsing. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Jan 2026 - **Updated:** 29 Jun 2026 - **Also known as:** ALSA-2026:0605, ALSA-2026:0606, ALSA-2026:0608, GHSA-6v4g-392h-r9mh, OESA-2026-1345, RHSA-2026:0605, RHSA-2026:0606, RHSA-2026:0608, RHSA-2026:4470, RHSA-2026:4477, RHSA-2026:4513, RHSA-2026:4522, RHSA-2026:4525, RHSA-2026:4543, RHSA-2026:4550, RHSA-2026:4553, RHSA-2026:4554, RLSA-2026:0605, RLSA-2026:0606, RLSA-2026:0608 ## What is CVE-2025-14242? CVE-2025-14242 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 14 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in vsftpd. This vulnerability allows a denial of service (DoS) via an integer overflow in the ls command parameter parsing, triggered by a remote, authenticated attacker sending a crafted STAT command with a specific byte sequence. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2025-14242? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `vsftpd` | AlmaLinux:10 | All versions | 3.0.5-10.el10_1.1 | | `vsftpd` | AlmaLinux:8 | All versions | 3.0.3-36.el8_10.3 | | `vsftpd` | AlmaLinux:9 | All versions | 3.0.5-6.el9_7.2 | | `vsftpd` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.0.5-10.el10_1.1 | | `vsftpd-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.0.5-10.el10_1.1 | | `vsftpd-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.0.5-10.el10_1.1 | | `vsftpd` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.3-36.el8_10.3 | | `vsftpd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.3-36.el8_10.3 | | `vsftpd-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.3-36.el8_10.3 | | `vsftpd` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.5-6.el9_7.2 | | `vsftpd-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.5-6.el9_7.2 | | `vsftpd-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.5-6.el9_7.2 | | `vsftpd` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.0.5-9.el10_0.1 | | `vsftpd-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.0.5-9.el10_0.1 | | `vsftpd-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.0.5-9.el10_0.1 | | `vsftpd` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.0.3-31.el8_2.1 | | `vsftpd-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.0.3-31.el8_2.1 | | `vsftpd-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.0.3-31.el8_2.1 | | `vsftpd` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.0.3-33.el8_4.1 | | `vsftpd-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.0.3-33.el8_4.1 | | `vsftpd-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.0.3-33.el8_4.1 | | `vsftpd` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.0.3-35.el8_6.1 | | `vsftpd-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.0.3-35.el8_6.1 | | `vsftpd-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.0.3-35.el8_6.1 | | `vsftpd` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.0.3-35.el8_6.1 | | `vsftpd-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.0.3-35.el8_6.1 | | `vsftpd-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.0.3-35.el8_6.1 | | `vsftpd` | Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.0.3-35.el8_8.1 | | `vsftpd-debuginfo` | Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.0.3-35.el8_8.1 | | `vsftpd-debugsource` | Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.0.3-35.el8_8.1 | | `vsftpd` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.0.3-49.el9_0.1 | | `vsftpd-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.0.3-49.el9_0.1 | | `vsftpd-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.0.3-49.el9_0.1 | | `vsftpd` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.0.5-4.el9_2.1 | | `vsftpd-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.0.5-4.el9_2.1 | | `vsftpd-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.0.5-4.el9_2.1 | | `vsftpd` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.0.5-5.el9_4.1 | | `vsftpd-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.0.5-5.el9_4.1 | | `vsftpd-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.0.5-5.el9_4.1 | | `vsftpd` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.0.5-6.el9_6.1 | ## How do I fix CVE-2025-14242? Apply the vendor's patch. ## Is CVE-2025-14242 being exploited? There is no known exploitation of CVE-2025-14242 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-14242 and fix it if it is affected. What it is: CVE-2025-14242 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 14 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-14242 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. 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-2025-14242/ (Markdown: https://insights.sbomify.com/CVE-2025-14242/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14242 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14242 - OSV: https://osv.dev/vulnerability/CVE-2025-14242 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-14242/ Summaries are generated and may contain mistakes; the official description above is the record.