# CVE-2018-25278: PicaJet FX 2.6.5 Denial of Service via Registration Fields

> Local attackers can crash PicaJet FX by submitting oversized input to registration fields, 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-wphv-9rxf-7x67

## What is CVE-2018-25278?

CVE-2018-25278 is a medium-severity denial of service vulnerability in PicaJet FX, 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

PicaJet FX 2.6.5 contains a denial of service vulnerability that allows local attackers to crash the application by submitting oversized input to registration fields. Attackers can paste a 6000-byte buffer into the Registration Name and Registration Key fields via the Help menu's Register PicaJet dialog to trigger an application crash.

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

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


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

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

## Is CVE-2018-25278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25278 is a medium-severity denial of service vulnerability in PicaJet FX, 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-25278 exists.

Affected product: PicaJet FX. 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-25278/ (Markdown: https://insights.sbomify.com/CVE-2018-25278/index.md)
```

## Sources

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

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