Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-10110: In version 3.23.0 of aimhubio/aim, the ScheduledStatusReporter object can be instantiated to run on the main t

49
This week
HIGH 7.5REMOTEDOWNGRADE

CVE-2024-10110 is a high-severity flaw (CVSS 7.5) affecting aim. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In version 3.23.0 of aimhubio/aim, the ScheduledStatusReporter object can be instantiated to run on the main thread of the tracking server, leading to the main thread being blocked indefinitely. This results in a denial of service as the tracking server becomes unable to respond to other requests.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 49%)
CISA exploited listNo
WeaknessCWE-400
Published2025-03-20
Last modified2026-06-17
Publisher (CNA): huntr.dev · Vendor: aimstack

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

aimstack aim DOWNGRADE
Affected: 3.23.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.23.0
1. Check installed version
pip show aim
2. No fixed release: DOWNGRADE to a release before 3.23.0
pip index versions aim pip install "aim<3.23.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-10110?

aim: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-10110 being exploited?

CVE-2024-10110 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-10110 affect?

CVE-2024-10110 affects aim. Severity is high (CVSS 7.5). In version 3.23.0 of aimhubio/aim, the ScheduledStatusReporter object can be instantiated to run on the main thread of the tracking server, leading to the main thread being blocked indefinitely. This results in a denial of service as the tr

How urgent is CVE-2024-10110?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.