# CVE-2026-4993: wandb OpenUI config.py hard-coded credentials

> Hard-coded credentials in wandb OpenUI allow local attackers to bypass security controls and access sensitive data.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-vf7r-qhhp-78wc

## What is CVE-2026-4993?

CVE-2026-4993 is a medium-severity vulnerability in wandb OpenUI, published on 28 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in wandb OpenUI up to 0.0.0.0/1.0. This impacts an unknown function of the file backend/openui/config.py. The manipulation of the argument LITELLM_MASTER_KEY leads to hard-coded credentials. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2026-4993 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4993 is a medium-severity vulnerability in wandb OpenUI, published on 28 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4993 exists.

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

## Sources

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

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