# CVE-2025-41257: Suprema BioStar 2 Insecure Password Change

> Attackers can change user passwords without knowing the current one, leading to unauthorized account access and potential system compromise.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 4 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-jj36-c637-m3x8

## What is CVE-2025-41257?

CVE-2025-41257 is a medium-severity authentication bypass vulnerability in Suprema BioStar 2, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Suprema’s BioStar 2 in version 2.9.11.6 allows users to set new password without providing the current one. Exploiting this flaw combined with other vulnerabilities can lead to unauthorized account access and potential system compromise.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-41257 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41257 is a medium-severity authentication bypass vulnerability in Suprema BioStar 2, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-41257 exists.

Affected product: Suprema BioStar 2. 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-41257/ (Markdown: https://insights.sbomify.com/CVE-2025-41257/index.md)
```

## Sources

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

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