Quick answers
- Is CVE-2024-6227 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-6227 being exploited in the wild.
- How severe is CVE-2024-6227?
- Low severity, with a CVSS score of 3, published 7 July 2026.
- Which products and versions are affected?
- aim (PyPI) ECOSYSTEM:introduced=0,last_affected=3.19.3.
- Is there a fix for CVE-2024-6227?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-6227 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-6227?
- Check whether you run aim (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an infinite loop (CWE-835) in the remote tracking server configuration logic. An attacker can configure the remote tracking server endpoint to point back to itself, causing the server to repeatedly connect to itself in an endless cycle. This requires network access to the server's configuration interface; no authentication bypass is demonstrated. The attack results in a denial of service as the server becomes unresponsive to other connections. The vulnerable code is located in aim/sdk/repo.py at line 195.
Affected products
- aimhubio Aim 0–3.19.3
Identifiers
- CVE-2024-6227
- GHSA-36h2-g4c8-9xcm
- PYSEC-2026-1081
Timeline
- 2024-07-08: disclosed
- 2024-08-07: advisory: GitHub reviewed