# CVE-2025-26486: Weak cryptography in Life 1st

> Weak password hashing allows attackers with hash access to brute-force credentials and take over accounts in Life 1st Identity Manager.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/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:** 19 Mar 2025
- **Updated:** 2 Jul 2025
- **Also known as:** GHSA-627p-vx8v-8v2c

## What is CVE-2025-26486?

CVE-2025-26486 is a medium-severity vulnerability in Beta80 Life 1st, published on 19 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Broken or Risky Cryptographic Algorithm, Use of Password Hash 
With Insufficient Computational Effort, Use of Weak Hash, Use of a 
One-Way Hash with a Predictable Salt vulnerabilities in Beta80 "Life 1st Identity Manager"
enable an attacker with access to
password hashes
to bruteforce user passwords or find a collision to ultimately while attempting to gain access to a target application that uses "Life 1st Identity Manager" as a service for authentication.
This issue affects Life 1st: 1.5.2.14234.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-760 (Use of a One-Way Hash with a Predictable Salt), CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

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

## Is CVE-2025-26486 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26486 is a medium-severity vulnerability in Beta80 Life 1st, published on 19 Mar 2025. 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-2025-26486 in the wild and no public exploit code.

Affected product: Beta80 Life 1st. 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-26486/ (Markdown: https://insights.sbomify.com/CVE-2025-26486/index.md)
```

## Sources

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

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