Skip to main content
VulnerabilityPublished Updated

CVE-2024-2195: Aim Web API vulnerable to Remote Code Execution

Affects aimSource GCVE Database

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 27 Oct 2026, 18:12 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIaimAffected
  • >=3.0.0 <=3.25.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the vulnerable endpoint and monitor for suspicious activity related to the /api/runs/search/run/ endpoint.

Description

A critical Remote Code Execution (RCE) vulnerability (CVE-2024-2195) affects the aim project versions 3.0.0 through 3.25.0. The flaw exists in the /api/runs/search/run/ endpoint due to improper access restriction in the run_search_api function, allowing attackers to execute arbitrary code via the query parameter. This can lead to full system compromise.

References

Community reviews

Loading reviews…