# CVE-2026-105832: EspoCRM before 10.0.6 Two-Factor Authentication Bypass on Unauthenticated Routes

> Attackers can bypass two-factor authentication on unauthenticated routes to read sensitive configuration parameters in EspoCRM.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-9h5f-ghfx-jfjc, GHSA-ph8v-hvf5-wgp9

## What is CVE-2026-105832?

CVE-2026-105832 is a medium-severity authentication bypass vulnerability in espocrm, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EspoCRM before 10.0.6 contains an authentication bypass vulnerability that accepts a login stopped at the second factor on routes not requiring authentication. Attackers knowing a 2FA-enabled user's username and password can skip the second factor to read config parameters not exposed publicly.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-105832 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105832 is a medium-severity authentication bypass vulnerability in espocrm, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105832 in the wild and no public exploit code.

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

## Sources

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

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