# CVE-2018-25286: Easy PhotoResQ 1.0 Buffer Overflow Denial of Service

> Local attackers can crash Easy PhotoResQ by inputting an excessively long string in the file options dialog, causing a denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-8hpc-x6cx-gqfq

## What is CVE-2018-25286?

CVE-2018-25286 is a medium-severity memory corruption vulnerability in Hdtune Easy PhotoResQ, published on 26 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Easy PhotoResQ 1.0 contains a buffer overflow vulnerability that allows local attackers to crash the application by supplying an excessively long string in the Folder/filename field. Attackers can input a 6000-byte payload through the File Options dialog to trigger a denial of service condition.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2018-25286?


## How do I fix CVE-2018-25286?

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

## Is CVE-2018-25286 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25286 and fix it if it is affected.

What it is: CVE-2018-25286 is a medium-severity memory corruption vulnerability in Hdtune Easy PhotoResQ, published on 26 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25286 exists.

Affected product: Hdtune Easy PhotoResQ. 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-2018-25286/ (Markdown: https://insights.sbomify.com/CVE-2018-25286/index.md)
```

## Sources

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

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