# CVE-2025-2129: Mage AI insecure default initialization of resource

> Mage AI contains insecure default resource initialization, potentially allowing security bypass, though the vendor disputes validity and will not fix it.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 9 Mar 2025
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-32cp-9h8g-xvhr

## What is CVE-2025-2129?

CVE-2025-2129 is a medium-severity vulnerability in Mage AI, published on 9 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecure default initialization of resource. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. After 7 months of repeated follow-ups by the researcher, Mage AI has decided to not accept this issue as a valid security vulnerability and has confirmed that they will not be addressing it.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2025-2129?


## How do I fix CVE-2025-2129?

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

## Is CVE-2025-2129 being exploited?

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

Public exploit code:

- Mage AI - Insecure Default Authentication Setup (nuclei): http/cves/2025/CVE-2025-2129.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2129 and fix it if it is affected.

What it is: CVE-2025-2129 is a medium-severity vulnerability in Mage AI, published on 9 Mar 2025. 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-2025-2129 exists.

Affected product: Mage AI. 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-2025-2129/ (Markdown: https://insights.sbomify.com/CVE-2025-2129/index.md)
```

## Sources

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

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