# CVE-2026-14850: Weak password recovery mechanism for forgotten password in MobiAPParc

> Attackers can reset passwords for arbitrary users by manipulating predictable user IDs, leading to unauthorized account takeover.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/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:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-vh5r-mqj2-86wg

## What is CVE-2026-14850?

CVE-2026-14850 is a high-severity authentication bypass vulnerability in MobiAPParc, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The password reset funcionality is vulnerable to unauthorized account modification due to improper validation of the user_id parameter. An attacker can manipulate this predictable numeric identifier to reset passwords for arbitrary users without proving account ownership.

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

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


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

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

## Is CVE-2026-14850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14850 is a high-severity authentication bypass vulnerability in MobiAPParc, published on 17 Sep 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-14850 in the wild and no public exploit code.

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

## Sources

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

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