dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-5003

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 was found in PromtEngineer localGPT up to 4d41c7d1713b16b216d8e062e51a5dd88b20b054. This affects the function handle_index of the file rag_system/api_server.py of the component Web Interface. Performing a manipulation results in information disclosure. It is possible to initiate the attack remotely. The exploit has been made public and could be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

An information disclosure vulnerability exists in the handle_index function of localGPT's web API server (rag_system/api_server.py). The flaw allows remote attackers to potentially access sensitive information through the web interface due to improper handling in the index handler.

MitigationImplement proper access controls and input validation in the handle_index function to prevent unauthorized information disclosure. Review all endpoints in the web interface for similar issues.

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
Low
Integrity
None
Availability
None

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

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. Verify localGPT installation and version
    Identify if localGPT is installed in your environment by checking for the project directory or installed package. Compare your installed version against the affected version range if known.
    Affected if localGPT is installed and running a version that contains the vulnerable handle_index function in rag_system/api_server.py
  2. Locate the affected API server file
    Find the file rag_system/api_server.py in your localGPT installation directory. This file contains the handle_index function that is vulnerable to information disclosure.
    Affected if The file rag_system/api_server.py exists in your installation and contains the handle_index function
  3. Confirm web API server is running
    Check if the localGPT web API server is currently running. This is typically started via a command like 'python -m rag_system.api_server' or similar startup scripts. Look for listening ports (commonly 8000 or 8080).
    Affected if The web API server is running and accessible over HTTP/HTTPS
  4. Identify if the index endpoint is exposed without authentication
    Inspect the handle_index function in rag_system/api_server.py to determine if it lacks proper authentication checks or access controls before returning sensitive information.
    Affected if The handle_index endpoint can be accessed without authentication and returns sensitive information
  5. Test the endpoint for information disclosure
    If the server is running, send a request to the index-related endpoint (such as /index or similar) without credentials and observe if sensitive data is returned.
    Affected if The endpoint returns sensitive information to unauthenticated users

You are affected if localGPT with the vulnerable handle_index function in rag_system/api_server.py is running and the web API server exposes the index endpoint without proper authentication, allowing unauthorized access to sensitive information.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper access controls and input validation in the handle_index function to prevent unauthorized information disclosure. Review all endpoints in the web interface for similar issues.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5003 — 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-5003 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