# CVE-2026-62232: Grav < 2.0.4 2FA Bypass via Secret Regeneration

> Attackers with valid passwords can bypass two-factor authentication in Grav CMS by overwriting the 2FA secret, effectively reducing security to password-only protection.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/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:** 17 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-4m9m-rmh9-2pgf

## What is CVE-2026-62232?

CVE-2026-62232 is a critical authentication bypass vulnerability in getgrav grav, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grav before 2.0.4 contains a two-factor authentication bypass vulnerability in the login plugin where the regenerate2FASecret task checks only user existence, not authorization, during the pending TOTP challenge window. Attackers who know the victim's password can call this task without a CSRF nonce to overwrite the 2FA secret with an attacker-chosen value, compute a valid TOTP code, and complete authentication while reducing 2FA to password-only protection.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-62232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62232 is a critical authentication bypass vulnerability in getgrav grav, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62232 exists.

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

## Sources

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

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