# CVE-2026-34408: Auth bypass in n/a

> Attackers can bypass password reset controls to set arbitrary passwords for any account if the user ID is known, leading to account takeover.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-338p-fcwm-8fgc

## What is CVE-2026-34408?

CVE-2026-34408 is a critical authentication bypass vulnerability in n/a, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Gambio 4.9.2.0 (patched in 2024-02 v1.0.0 for GX4 v4.0.0.0 to v4.9.2.0). The password reset function can be bypassed to set arbitrary passwords for arbitrary accounts if the ID is known.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-34408 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34408 is a critical authentication bypass vulnerability in n/a, published on 5 May 2026. 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-2026-34408 in the wild and no public exploit code.

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

## Sources

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

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