wandb OpenUI up to 0.0.0.0/1.0 backend/openui/config.py LITELLM_MASTER_KEY hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 1.36 |
Summary
A vulnerability, which was classified as critical, was found in wandb OpenUI up to 0.0.0.0/1.0. Affected is an unknown function of the file backend/openui/config.py. The manipulation of the argument LITELLM_MASTER_KEY results in hard-coded credentials. This vulnerability is known as CVE-2026-4993. Attacking locally is a requirement. Furthermore, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability classified as problematic has been found in wandb OpenUI up to 0.0.0.0/1.0. Affected is some unknown functionality of the file backend/openui/config.py. The manipulation of the argument LITELLM_MASTER_KEY with an unknown input leads to a hard-coded credentials vulnerability. CWE is classifying the issue as CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. This is going to have an impact on confidentiality.
The advisory is shared for download at gist.github.com. This vulnerability is traded as CVE-2026-4993. The exploitability is told to be easy. The attack needs to be approached locally. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1110.001.
The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-16913). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/27/2026 Advisory disclosed03/27/2026 VulDB entry created
03/28/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-4993 (🔒)
GCVE (CVE): GCVE-0-2026-4993
GCVE (VulDB): GCVE-100-353880
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/27/2026 14:53Updated: 03/28/2026 19:06
Changes: 03/27/2026 14:53 (57), 03/28/2026 19:06 (1)
Complete: 🔍
Submitter: Eric-b
Cache ID: 216:F46:103
Submit
Accepted
- Submit #778265: Weights and Biases OpenUI <= 1.0 (commit f9d8f0e) Use of Hard-coded Credentials (CWE-798) (by Eric-b)
No comments yet. Languages: en.
Please log in to comment.