# CVE-2024-10624: Regular Expression Denial of Service (ReDoS) in gradio-app/gradio

> Attackers can cause server CPU exhaustion and denial of service via crafted input in the gradio library's datetime component.

- **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-rvgh-pr46-x7gg, PYSEC-2026-1421

## What is CVE-2024-10624?

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

### Official description

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the gradio-app/gradio repository, affecting the gr.Datetime component. The affected version is git commit 98cbcae. The vulnerability arises from the use of a regular expression `^(?:\s*now\s*(?:-\s*(\d+)\s*([dmhs]))?)?\s*$` to process user input. In Python's default regex engine, this regular expression can take polynomial time to match certain crafted inputs. An attacker can exploit this by sending a crafted HTTP request, causing the gradio process to consume 100% CPU and potentially leading to a Denial of Service (DoS) condition on the server.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2024-10624?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | From 4.38.0 to 5.0.0-beta.2 | None |
| `gradio` | PyPI | From 4.38.0 to 5.0.0-beta.2 | None |
| `gradio` | PyPI | From 4.38.0 to 5.0.0-beta.2 | None |

Products: Gradio Project Gradio.

## How do I fix CVE-2024-10624?

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

## Is CVE-2024-10624 being exploited?

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

## Other vulnerabilities in Gradio Project Gradio

- [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8)
- [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6)
- [CVE-2022-24770](https://insights.sbomify.com/CVE-2022-24770/): Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging (high 8.8)
- [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7)
- [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10624 and fix it if it is affected.

What it is: CVE-2024-10624 is a high-severity denial of service vulnerability in Gradio Project Gradio, 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-2024-10624 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected from 4.38.0 up to 5.0.0-beta.2; no fix listed
- gradio (PyPI): affected from 4.38.0 up to 5.0.0-beta.2; no fix listed
- gradio (PyPI): affected from 4.38.0 up to 5.0.0-beta.2; 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-2024-10624/ (Markdown: https://insights.sbomify.com/CVE-2024-10624/index.md)
```

## Sources

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

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