# CVE-2025-0189: Denial of Service in aimhubio/aim

> An attacker can cause a denial of service by sending large images to the AIM tracking server, which overrides websocket message size limits.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-j5qj-rg5j-j7c2, PYSEC-2026-1089

## What is CVE-2025-0189?

CVE-2025-0189 is a high-severity denial of service vulnerability in aimhubio/aim, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In version 3.25.0 of aimhubio/aim, the tracking server is vulnerable to a denial of service attack. The server overrides the maximum size for websocket messages, allowing very large images to be tracked. This causes the server to become unresponsive to other requests while processing the large image, leading to a denial of service condition.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

3 open source packages ship an affected version, including aim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aim` | PyPI | All versions to 3.25.0 | None |
| `aim` | PyPI | All versions to 3.25.0 | None |
| `aim` | PyPI | All versions to 3.25.0 | None |

Products: Aimstack Aim.

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

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

## Is CVE-2025-0189 being exploited?

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

## Other vulnerabilities in aimhubio/aim

- [CVE-2024-6396](https://insights.sbomify.com/CVE-2024-6396/): Arbitrary File Overwrite and Data Exfiltration in aimhubio/aim (critical 9.8)
- [CVE-2024-2195](https://insights.sbomify.com/CVE-2024-2195/): Remote Code Execution in aimhubio/aim (critical 9.8)
- [CVE-2024-6829](https://insights.sbomify.com/CVE-2024-6829/): Arbitrary File Overwrite through tarfile-extraction in aimhubio/aim (critical 9.1)
- [CVE-2024-8769](https://insights.sbomify.com/CVE-2024-8769/): Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim (critical 9.1)
- [CVE-2025-51464](https://insights.sbomify.com/CVE-2025-51464/): Aim vulnerable to Cross-site Scripting (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0189 is a high-severity denial of service vulnerability in aimhubio/aim, published on 20 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-0189 exists.

Affected packages and fixed versions:
- aim (PyPI): affected all versions up to 3.25.0; no fix listed
- aim (PyPI): affected all versions up to 3.25.0; no fix listed
- aim (PyPI): affected all versions up to 3.25.0; no fix listed

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-0189/ (Markdown: https://insights.sbomify.com/CVE-2025-0189/index.md)
```

## Sources

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

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