# CVE-2024-7779: ReDoS (Regular Expression Denial of Service) in danswer-ai/danswer

> An attacker can cause a denial of service in the Danswer AI application by triggering inefficient regular expression processing.

- **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-4f3h-89pj-w84f

## What is CVE-2024-7779?

CVE-2024-7779 is a high-severity denial of service vulnerability in danswer-ai/danswer, 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 vulnerability in danswer-ai/danswer version 1 allows an attacker to perform a Regular Expression Denial of Service (ReDoS) by manipulating regular expressions. This can significantly slow down the application's response time and potentially render it completely unusable.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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


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

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

## Is CVE-2024-7779 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7779 is a high-severity denial of service vulnerability in danswer-ai/danswer, 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-7779 exists.

Affected product: danswer-ai/danswer. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-7779/ (Markdown: https://insights.sbomify.com/CVE-2024-7779/index.md)
```

## Sources

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

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