dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-0182

HIGH · 7.5 CVSS v3.0 Published 2025-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in danswer-ai/danswer version 0.9.0 allows for denial of service through memory exhaustion. The issue arises from the use of a vulnerable version of the starlette package (<=0.49) via fastapi, which was patched in fastapi version 0.115.3. The vulnerability can be exploited by sending multiple requests to the /auth/saml/callback endpoint, leading to uncontrolled memory consumption and eventual denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A memory exhaustion denial of service vulnerability exists in danswer-ai/danswer version 0.9.0 due to a vulnerable starlette dependency (<=0.49) passed through fastapi. The vulnerability is triggered by sending multiple requests to the /auth/saml/callback endpoint, causing uncontrolled memory consumption and eventual service unavailability.

MitigationUpgrade danswer to a version that includes fastapi >= 0.115.3 (which contains patched starlette), or manually update the starlette and fastapi dependencies to patched versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed danswer version
    Run the command to display the installed danswer version (e.g., pip show danswer-ai or check the running service version)
    Affected if The installed version is exactly 0.9.0 or falls within the affected range based on version comparison
  2. Confirm SAML authentication is enabled
    Inspect the danswer configuration files or environment variables to verify that SAML-based authentication is configured and the /auth/saml/callback endpoint is active
    Affected if SAML authentication is enabled and the vulnerable endpoint is accessible
  3. Check starlette dependency version
    Inspect the installed starlette package version (e.g., pip show starlette or check the requirements/poetry lock file)
    Affected if The installed starlette version is 0.49 or lower (any version <=0.49)
  4. Check fastapi dependency version
    Inspect the installed fastapi package version to understand the starlette dependency chain (e.g., pip show fastapi)
    Affected if Fastapi version is below 0.115.3, which would bundle an unpatched starlette

A user is affected if running danswer 0.9.0 with SAML authentication enabled and the starlette dependency is version 0.49 or lower (or fastapi version below 0.115.3), allowing uncontrolled memory consumption via the /auth/saml/callback endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade danswer to a version that includes fastapi >= 0.115.3 (which contains patched starlette), or manually update the starlette and fastapi dependencies to patched versions.

Recommended fix Moderate confidence

Upgrade fastapi to >=0.115.3 (which pulls patched starlette >0.49)

  1. Check the current fastapi version installed in the danswer environment (e.g., pip show fastapi or查看requirements.txt)
  2. Upgrade fastapi to version 0.115.3 or higher by running: pip install 'fastapi>=0.115.3'
  3. Verify the upgraded fastapi version includes a patched starlette version (should be >0.49)
  4. Restart the danswer application services to load the updated dependencies
  5. Test the /auth/saml/callback endpoint to confirm the application remains functional after the update
Caveat Minor - fastapi 0.115.x may have backward compatibility changes; verify danswer functionality after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data