# CVE-2019-25358: FileOptimizer 14.00.2524 - Denial of Service

> Attackers can crash FileOptimizer by overwriting the TempDirectory parameter in the configuration file with a large buffer.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 19 Feb 2026
- **Also known as:** GHSA-4vww-ch2x-c53p

## What is CVE-2019-25358?

CVE-2019-25358 is a high-severity denial of service vulnerability in nikkhokkho FileOptimizer, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileOptimizer 14.00.2524 contains a denial of service vulnerability that allows attackers to crash the application by manipulating the FileOptimizer32.ini configuration file. Attackers can overwrite the TempDirectory parameter with a 5000-character buffer to cause the application to crash when opening options.

Weakness: CWE-1282 (Assumed-Immutable Data is Stored in Writable Memory)

## Which versions are affected by CVE-2019-25358?


## How do I fix CVE-2019-25358?

No fix has been published for CVE-2019-25358 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25358 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25358 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25358 and fix it if it is affected.

What it is: CVE-2019-25358 is a high-severity denial of service vulnerability in nikkhokkho FileOptimizer, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25358 exists.

Affected product: nikkhokkho FileOptimizer. 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-2019-25358/ (Markdown: https://insights.sbomify.com/CVE-2019-25358/index.md)
```

## Sources

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

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