# CVE-2026-19218: Password Reset Code Brute Force Leading to Account Takeover in AKIN Software's MyRezzta

> Attackers can brute force weak password reset codes to take over user accounts in MyRezzta.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-m33r-p2j3-r4pf

## What is CVE-2026-19218?

CVE-2026-19218 is a critical authentication bypass vulnerability in AKIN Software Computer Import-Export Industry and Trade Co. Ltd. MyRezzta, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Weak Password Recovery Mechanism for Forgotten Password vulnerability in AKIN Software Computer Import-Export Industry and Trade Co. Ltd. MyRezzta allows Password Recovery Exploitation.

This issue affects MyRezzta: from 2.06.03 before 2.07.01.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-19218 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19218 is a critical authentication bypass vulnerability in AKIN Software Computer Import-Export Industry and Trade Co. Ltd. MyRezzta, published on 8 Oct 2026. 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-2026-19218 in the wild and no public exploit code.

Affected product: AKIN Software Computer Import-Export Industry and Trade Co. Ltd. MyRezzta. 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-19218/ (Markdown: https://insights.sbomify.com/CVE-2026-19218/index.md)
```

## Sources

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

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