# CVE-2026-4994: wandb OpenUI APIStatusError server.py generic_exception_handler information exposure

> Attackers on the local network can trigger error messages in wandb OpenUI to expose sensitive information via the APIStatusError handler.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/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-g7rm-9pjx-q3vg

## What is CVE-2026-4994?

CVE-2026-4994 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 was found in wandb OpenUI up to 1.0/3.5-turb. Affected is the function generic_exception_handler of the file backend/openui/server.py of the component APIStatusError Handler. The manipulation of the argument key results in information exposure through error message. Access to the local network is required for this attack. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-4994 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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