dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-6588

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 weakness has been identified in serge-chat serge up to 1.4TB. The impacted element is the function download_model/delete_model of the file api/src/serge/routers/model.py of the component Model API Endpoint. Executing a manipulation can lead to missing authentication. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. 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

The serge-chat application has a missing authentication vulnerability in the Model API Endpoint (api/src/serge/routers/model.py). The download_model and delete_model functions lack proper authentication checks, allowing unauthenticated remote attackers to download or delete ML models stored in the system.

MitigationImplement authentication and authorization checks on the model download and delete API endpoints. Additionally, validate user permissions before allowing model manipulation operations and consider adding audit logging for these sensitive functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 serge-chat is deployed
    Search for the serge-chat application in your environment, look for the api/src/serge/routers/model.py file, or check for processes/named containers running serge-chat
    Affected if The serge-chat application is present in your environment
  2. Check the installed version
    Look for version information in package.json, pyproject.toml, setup.py, or run 'pip show serge-chat' or check the git repository tag if available
    Affected if The version cannot be determined or is prior to the patch date for this vulnerability
  3. Inspect the model.py source code
    Examine api/src/serge/routers/model.py and locate the download_model and delete_model function definitions. Check if they have authentication decorators (e.g., @require_auth, Depends(authenticate)) or if authentication is checked within the function body
    Affected if The download_model and delete_model functions lack authentication decorators or authentication logic checks
  4. Verify API route configuration
    Check the router registration in model.py to see how the endpoints are defined (e.g., @router.post/GET). Then examine if the parent router or FastAPI app has authentication middleware applied to these routes
    Affected if The /model/download and /model/delete endpoints (or similar paths) are not protected by authentication requirements
  5. Test endpoint accessibility
    If safe to do so in a non-production environment, send an unauthenticated HTTP request to the model download and delete endpoints (typically /api/model/download/{model_name} or /api/model/delete/{model_name}) and observe if the operation succeeds without credentials
    Affected if The endpoints return successful responses (200/OK) without providing authentication tokens

Your environment is affected if serge-chat is deployed and the download_model/delete_model functions in api/src/serge/routers/model.py lack authentication checks or are not protected by authentication middleware.

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 authentication and authorization checks on the model download and delete API endpoints. Additionally, validate user permissions before allowing model manipulation operations and consider adding audit logging for these sensitive functions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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