# CVE-2026-107180: MISP: Forced TOTP Enrolment Bypassed via Non-Browser Request Types on otp_required Instances

> Authenticated users on MISP instances with mandatory TOTP can bypass enrollment via non-browser requests, retaining full access without second-factor authentication.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-jgf2-xf9x-w72j

## What is CVE-2026-107180?

CVE-2026-107180 is a high-severity authentication bypass vulnerability in MISP, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On MISP instances configured to require TOTP enrolment (Security.otp_required), the enforcement of the mandatory two-factor authentication setup applied only to standard browser requests. An authenticated user who had not yet enrolled in TOTP could bypass the forced setup by issuing any non-browser request type, including AJAX/XHR calls, REST API requests, .json format URLs, restSearch queries, or automation actions. Because these machine-readable request shapes cannot follow the redirect that the browser path uses to send the user to the TOTP enrolment page, the guard simply skipped the check and the user retained full access to the instance without completing the required second-factor setup.

The initial fix (commit 8deb0619e) added a guard specifically for AJAX requests. A follow-up fix (commit 6b527ba6e) broadened the guard to cover every non-browser request shape, while preserving the exemption for identities authenticated via API key (logged_by_authkey flag).

Impact: an authenticated user on an otp_required instance can operate with full access indefinitely without enrolling in TOTP, nullifying the instance-level two-factor authentication policy.

Affected version: <2.5.48

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-107180 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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