dbcve.org
DeepauditApplication · Lintsinghua

CVE-2026-2532

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-16
Fix available
A fix is available. Upgrade to after 3.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 was detected in lintsinghua DeepAudit up to 3.0.3. This issue affects some unknown processing of the file backend/app/api/v1/endpoints/embedding_config.py of the component IP Address Handler. Performing a manipulation results in server-side request forgery. It is possible to initiate the attack remotely. Upgrading to version 3.0.4 and 3.1.0 is capable of addressing this issue. The patch is named da853fdd8cbe9d42053b45d83f25708ba29b8b27. It is suggested to upgrade the affected component.

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

Server-side request forgery (SSRF) vulnerability in the IP Address Handler component of backend/app/api/v1/endpoints/embedding_config.py in lintsinghua DeepAudit up to version 3.0.3 allows remote attackers to craft malicious requests and make the server perform arbitrary network requests to internal or external resources.

MitigationUpgrade DeepAudit to version 3.0.4 or 3.1.0 to apply the patch (da853fdd8cbe9d42053b45d83f25708ba29b8b27), which addresses the SSRF vulnerability in the embedding configuration endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DeepauditApplication
Affected:<= 3.0.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 DeepAudit version
    Locate the version information for your DeepAudit installation (check version file, package metadata, or application startup logs) and note the exact version number
    Affected if version is 3.0.3 or earlier (any version <= 3.0.3)
  2. Locate embedding_config.py endpoint
    Search the DeepAudit installation directory for the embedding_config.py file and verify the API endpoint handler is present in the codebase
    Affected if the file embedding_config.py exists and exposes an API endpoint
  3. Confirm IP Address Handler component is enabled
    Examine the embedding_config.py configuration to determine whether the IP Address Handler component is actively loaded or enabled in the running application
    Affected if IP Address Handler component is enabled and accessible via the API
  4. Verify API endpoint is network-accessible
    Check network configuration and firewall rules to determine if the embedding_config.py API endpoint is exposed to network requests (internal or external)
    Affected if the endpoint is reachable from network (not localhost-only or firewall-blocked)

You are affected if your DeepAudit version is 3.0.3 or earlier AND the embedding_config.py API endpoint with IP Address Handler is network-accessible in your environment.

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
Upgrade available Upgrade to a release after 3.0.3
Vendor patch github.com →
Interim mitigation

Upgrade DeepAudit to version 3.0.4 or 3.1.0 to apply the patch (da853fdd8cbe9d42053b45d83f25708ba29b8b27), which addresses the SSRF vulnerability in the embedding configuration endpoint.

Recommended fix High confidence

3.0.4 or 3.1.0

  1. Confirm current Deepaudit version by checking installed package or application metadata
  2. Upgrade Deepaudit to version 3.0.4 or 3.1.0 (either version contains the fix)
  3. If using pip: run 'pip install deepaudit==3.0.4' or 'pip install deepaudit==3.1.0'
  4. If using source: pull the latest code from the repository and reinstall
  5. Verify the upgrade was successful by checking the new version number
  6. Test that the embedding_config.py endpoint no longer allows arbitrary URL manipulation

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

Fix this in Deepaudit 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 the upgrade done

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-2026-2532 — 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-2026-2532 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