# CVE-2025-27787: Applio allows a DoS in restart.py > Attackers can cause denial of service by killing arbitrary processes via crafted config files, potentially crashing the application and other system services. - **Severity:** High 7.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 19 Mar 2025 - **Updated:** 20 Mar 2025 ## What is CVE-2025-27787? CVE-2025-27787 is a high-severity denial of service vulnerability in IAHispano Applio, published on 19 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Applio is a voice conversion tool. Versions 3.2.8-bugfix and prior are vulnerable to denial of service (DoS) in restart.py. `model_name` in train.py takes user input, and passes it to the `stop_train` function in restart.py, which uses it construct a path to a folder with `config.json`. That `config.json` is opened and the list of values under "process_pids" are read. Next all the process IDs listed in the JSON are killed. Using one of the arbitrary file writes, one can write to `logs/foobar` a `config.json` file, which contains a list of process IDs. Then one can access this endpoint to kill these processes. Since an attacker can't know what process is running on which process ID, they can send a list of hundreds of process IDs, which can kill the process that applio is using to run, as well as other, potentially important processes, which leads to DoS. Note that constructing a path with user input also enables path traversal. For example, by supplying "../../" in `model_name` one can access `config.json` freom locations two folders down on the server. As of time of publication, no known patches are available. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-27787? It affects 1 product. Products: Applio Applio. ## How do I fix CVE-2025-27787? No fix has been published for CVE-2025-27787 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-27787 being exploited? There is no known exploitation of CVE-2025-27787 in the wild and no public exploit code. ## Other vulnerabilities in IAHispano Applio - [CVE-2025-27778](https://insights.sbomify.com/CVE-2025-27778/): Applio allows unsafe deserialization in infer.py (high 8.9) - [CVE-2025-27779](https://insights.sbomify.com/CVE-2025-27779/): Applio allows unsafe deserialization in model_blender.py (high 8.9) - [CVE-2025-27780](https://insights.sbomify.com/CVE-2025-27780/): Applio allows unsafe deserialization in model_information.py (high 8.9) - [CVE-2025-27781](https://insights.sbomify.com/CVE-2025-27781/): Applio allows unsafe deserialization in inference.py (high 8.9) - [CVE-2025-27774](https://insights.sbomify.com/CVE-2025-27774/): Applio allows SSRF and file write in model_download.py (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-27787 and fix it if it is affected. What it is: CVE-2025-27787 is a high-severity denial of service vulnerability in IAHispano Applio, published on 19 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-27787 in the wild and no public exploit code. Affected product: IAHispano Applio. 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-27787/ (Markdown: https://insights.sbomify.com/CVE-2025-27787/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27787 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27787 - OSV: https://osv.dev/vulnerability/CVE-2025-27787 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-27787/ Summaries are generated and may contain mistakes; the official description above is the record.