# CVE-2021-26253: Bypass of Splunk Enterprise's implementation of DUO MFA

> Attackers can bypass DUO MFA verification in Splunk Enterprise instances configured to use this feature, potentially gaining unauthorized access.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2393-5754-m287

## What is CVE-2021-26253?

CVE-2021-26253 is a high-severity authentication bypass vulnerability in Splunk Splunk, published on 6 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential vulnerability in Splunk Enterprise's implementation of DUO MFA allows for bypassing the MFA verification in Splunk Enterprise versions before 8.1.6. The potential vulnerability impacts Splunk Enterprise instances configured to use DUO MFA and does not impact or affect a DUO product or service.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-26253?

It affects 1 product.


Products: Splunk Splunk.

## How do I fix CVE-2021-26253?

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

## Is CVE-2021-26253 being exploited?

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

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26253 and fix it if it is affected.

What it is: CVE-2021-26253 is a high-severity authentication bypass vulnerability in Splunk Splunk, published on 6 May 2022. 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-2021-26253 in the wild and no public exploit code.

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

## Sources

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

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