# CVE-2026-25250: Security feature bypass in EazyFix

> Attackers can bypass Secure Boot protection in EazyFix due to a missing cryptographic step, compromising system integrity.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-4rwm-w4qm-p8q2

## What is CVE-2026-25250?

CVE-2026-25250 is a medium-severity vulnerability in eazsolution EazyFix, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EAZ EazyFix 12.9 allows a Security Feature Bypass related to a "Missing Cryptographic Step" associated with "Secure Boot disable."

Weakness: CWE-325 (Missing Cryptographic Step)

## Which versions are affected by CVE-2026-25250?


## How do I fix CVE-2026-25250?

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

## Is CVE-2026-25250 being exploited?

There is no known exploitation of CVE-2026-25250 in the wild and no public exploit code.

Public exploit code:

- Analysis and exploit for CVE-2026-25250, a Secure Boot bypass in Horizon DataSys Reboot Restore where shdloader.efi loads Shield.efi without verification. (github_poc): https://github.com/TheMalwareGuardian/CVE-2026-25250

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25250 and fix it if it is affected.

What it is: CVE-2026-25250 is a medium-severity vulnerability in eazsolution EazyFix, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25250 in the wild and no public exploit code.

Affected product: eazsolution EazyFix. 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-2026-25250/ (Markdown: https://insights.sbomify.com/CVE-2026-25250/index.md)
```

## Sources

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

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