dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-50891

HIGH · 8.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Incorrect access control in the /admin/api/config component of Filestash v0.4.0 allows attackers to escalate privileges via sending a crafted request.

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

Incorrect access control in the /admin/api/config endpoint of Filestash v0.4.0 allows unauthenticated or low-privilege attackers to send crafted requests that bypass authorization checks, enabling privilege escalation to admin-level access.

MitigationUpgrade Filestash to the latest patched version. Until then, restrict network access to admin API endpoints and implement additional authentication layers such as API keys or VPN controls.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify Filestash version
    Check the running Filestash instance version by reviewing the Docker container tag, the application startup logs, or querying the /api/version endpoint if available
    Affected if The installed version is 0.4.0 or falls within the v0.4.x release line
  2. Verify /admin/api/config endpoint exposure
    Attempt to access the /admin/api/config endpoint from the Filestash server using curl or a similar HTTP client (e.g., curl -s http://localhost:8334/admin/api/config)
    Affected if The endpoint returns any HTTP response without requiring authentication credentials
  3. Confirm authentication enforcement
    Send a request to /admin/api/config without including session cookies, API keys, or Authorization headers and inspect the HTTP response code
    Affected if The server returns a 200 OK or exposes configuration data instead of returning 401 Unauthorized or 403 Forbidden
  4. Check authorization controls
    Log in with a low-privilege or non-admin user account and attempt a POST request to /admin/api/config with a benign payload to test if privilege escalation is possible
    Affected if The low-privilege user can successfully modify configuration settings or access admin-level data through this endpoint

You are affected if running Filestash v0.4.0 and the /admin/api/config endpoint is accessible without valid admin authentication.

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

Upgrade Filestash to the latest patched version. Until then, restrict network access to admin API endpoints and implement additional authentication layers such as API keys or VPN controls.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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