# CVE-2025-57197: Auth bypass in n/a

> A local attacker with root access can bypass PIN verification to change the authentication PIN in the Payeer Android app.


- **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:** 29 Sep 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-f9rv-f6xg-xq3j

## What is CVE-2025-57197?

CVE-2025-57197 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Payeer Android application 2.5.0, an improper access control vulnerability exists in the authentication flow for the PIN change feature. A local attacker with root access to the device can dynamically instrument the app to bypass the current PIN verification check and directly modify the authentication PIN. This allows unauthorized users to change PIN without knowing the original/current PIN.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-57197?


## How do I fix CVE-2025-57197?

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

## Is CVE-2025-57197 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57197 and fix it if it is affected.

What it is: CVE-2025-57197 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Sep 2025. 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-2025-57197 exists.

Affected product: n/a. 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-2025-57197/ (Markdown: https://insights.sbomify.com/CVE-2025-57197/index.md)
```

## Sources

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

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