# CVE-2026-41660: Admidio: Inverted 2FA Reset Authorization Check Lets Group Leaders Strip Admin TOTP

> Group leaders can strip administrators' two-factor authentication due to an inverted authorization check, enabling account takeover.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-rh3w-4ccx-prf9

## What is CVE-2026-41660?

CVE-2026-41660 is a high-severity missing authorization vulnerability in admidio, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Admidio is an open-source user management solution. Prior to version 5.0.9, a logic error in Admidio's two-factor authentication reset inverts the authorization check. Non-admin users cannot remove their own TOTP configuration, but they can remove other users' TOTP, including administrators. A group leader with profile edit rights on an admin account can strip that admin's 2FA. This issue has been patched in version 5.0.9.

Weakness: CWE-863 (Incorrect Authorization)

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

2 open source packages ship an affected version, including admidio/admidio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | All versions | 5.0.9 |
| `admidio/admidio` | Packagist | All versions | 5.0.9 |

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

Upgrade admidio/admidio to 5.0.9 or later.

## Is CVE-2026-41660 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41660 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41660 is a high-severity missing authorization vulnerability in admidio, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41660 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.9
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.9

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

## Sources

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

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