dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-5000

HIGH · 7.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 →
82/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 was detected in PromtEngineer localGPT up to 4d41c7d1713b16b216d8e062e51a5dd88b20b054. Impacted is the function LocalGPTHandler of the file backend/server.py of the component API Endpoint. The manipulation of the argument BaseHTTPRequestHandler results in missing authentication. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. 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

A missing authentication vulnerability exists in the LocalGPTHandler function of the API endpoint in PromtEngineer localGPT (up to commit 4d41c7d). The API endpoint accepts requests without requiring any authentication, allowing remote attackers to access the LocalGPT functionality without credentials.

MitigationImplement proper authentication and authorization checks in the LocalGPTHandler function and all API endpoints to verify user identity before processing requests.

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

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

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 if PromtEngineer localGPT is deployed
    Locate the localGPT installation directory and confirm the product name matches 'PromtEngineer localGPT' or contains the LocalGPTHandler component
    Affected if The product is PromtEngineer localGPT with the LocalGPTHandler function present in the codebase
  2. Determine the git commit version
    Run 'git log --oneline' in the localGPT repository root to view commit history, or check for version metadata files that reference commit hashes
    Affected if The installed commit is 4d41c7d or any earlier commit (the vulnerability affects up to and including commit 4d41c7d)
  3. Locate the LocalGPTHandler function
    Search the codebase for the string 'LocalGPTHandler' using grep or a file search (e.g., 'grep -r "LocalGPTHandler" .' or similar)
    Affected if The LocalGPTHandler function exists in the codebase and is part of the API endpoint handling
  4. Inspect API endpoint authentication configuration
    Examine the API routing/configuration files where LocalGPTHandler is registered as an endpoint; look for middleware, decorators, or checks that enforce authentication (e.g., @auth_required, session validation, token checks)
    Affected if The API endpoint associated with LocalGPTHandler has no authentication middleware or validation logic present
  5. Test endpoint accessibility without credentials
    Send an HTTP request to the LocalGPTHandler API endpoint using curl or similar tool without including any authentication headers, tokens, or cookies
    Affected if The endpoint responds successfully (returns 2xx or valid data) without any authentication credentials provided

If PromtEngineer localGPT is running at commit 4d41c7d or earlier and the LocalGPTHandler API endpoint responds to requests without requiring authentication credentials, the environment is affected by this vulnerability.

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

Implement proper authentication and authorization checks in the LocalGPTHandler function and all API endpoints to verify user identity before processing requests.

Recommended fix Moderate confidence

Latest commit after 4d41c7d1713b16b216d8e062e51a5dd88b20b054 (main branch)

  1. 1. Navigate to the localGPT repository directory
  2. 2. Check the current commit: git log -1 --oneline
  3. 3. Verify if the current commit is at or before 4d41c7d1713b16b216d8e062e51a5dd88b20b054
  4. 4. If vulnerable, pull the latest code: git pull origin main (or git fetch --all && git reset --hard origin/main)
  5. 5. Ensure the API endpoint in backend/server.py now includes authentication checks in the LocalGPTHandler function
  6. 6. Test that unauthenticated requests to the API endpoint are now rejected
Caveat None expected for authentication addition; may need to configure credentials if API now requires auth

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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