# CVE-2025-26485: Information disclosure in Life 1st

> Attackers can enumerate valid users in Beta80 Life 1st by analyzing distinct error messages returned for failed authentication attempts.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/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:** 19 Mar 2025
- **Updated:** 2 Jul 2025
- **Also known as:** GHSA-6mx4-qxhj-cjh2

## What is CVE-2025-26485?

CVE-2025-26485 is a medium-severity vulnerability in Beta80 Life 1st, published on 19 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Beta80 Life 1st enables the retrieval of different error messages for failed authentication attempts 
(in case of the usage of a wrong password or a non existent user). The difference in the 
returned error messages could be used by attackers to understand whether a 
certain user is registered in the Identity Manager.

This issue affects Life 1st: 1.5.2.14234.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-26485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26485 is a medium-severity vulnerability in Beta80 Life 1st, published on 19 Mar 2025. 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-2025-26485 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-26485/ (Markdown: https://insights.sbomify.com/CVE-2025-26485/index.md)
```

## Sources

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

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