# CVE-2026-57867: Auth bypass in MicroRealEstate

> Attackers can bypass authentication by brute-forcing One-Time Passwords due to missing token state management, allowing unauthorized access to user accounts.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-j5cw-4r7c-4vw8

## What is CVE-2026-57867?

CVE-2026-57867 is a high-severity authentication bypass vulnerability in MicroRealEstate, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MicroRealEstate allows adversaries to bypass authentication due to a lack of token state management. This would permit adversaries targeting MicroRealEstate deployments to brute-force One-Time Passwords (OTP) to log in as any user. This issue affects MicroRealEstate: through 1.0.0-alpha3.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-57867 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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