Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API

CVE-2026-69160GHSA-86cx-wwf4-phq4

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/OpenListTeam/OpenList

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/OpenListTeam/OpenList/v3

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/OpenListTeam/OpenList/v4

    Affected
    <= 4.2.3
    Fixed in
    4.2.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-69160: 0.40% estimated exploitation activity in the next 30 days; percentile 34.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary An authorization bypass vulnerability exists in the file sharing mechanism of Openlist. Due to a flawed, non-separator-aware path validation check, an authenticated user can create share links for files outside their restricted base directory. This allows an attacker to bypass tenant/user isolation and gain unauthorized read access to arbitrary files within the system. Details When a user attempts to create or update a file share, the application must verify that the requested file path falls within the user's assigned BasePath. However, in server/handles/sharing.go, this authorization check relies on a simple string prefix function: strings.HasPrefix(requestedpath, user.BasePath). Because strings.HasPrefix does not account for directory separators (e.g., /), an attacker whose BasePath is assigned to /base can supply a target path like /base2/secretdocument.txt. The validation strings.HasPrefix("/base2/secretdocument.txt", "/base") evaluates to true, successfully passing the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-86cx-wwf4-phq4

  2. Revision 1 · created ·

    Published from osv record GO-2026-6109

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-69160

Advisory: OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API
IDs: CVE-2026-69160, GHSA-86cx-wwf4-phq4
Record: https://patchnext.com/advisories/cve-2026-69160 (revision 2, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/OpenListTeam/OpenList/v4 4.2.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/OpenListTeam/OpenList: affected every version
- Go github.com/OpenListTeam/OpenList/v3: affected every version
- Go github.com/OpenListTeam/OpenList/v4: affected <= 4.2.3; fixed in 4.2.4

## Suggested inspection (read-only)
- Go github.com/OpenListTeam/OpenList: check the installed version with your package manager.
- Go github.com/OpenListTeam/OpenList/v3: check the installed version with your package manager.
- Go github.com/OpenListTeam/OpenList/v4: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/OpenListTeam/OpenList, github.com/OpenListTeam/OpenList/v3, github.com/OpenListTeam/OpenList/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6109 (OSV record GO-2026-6109 lists affected ranges: Go github.com/OpenListTeam/OpenList >=0; Go github.com/OpenListTeam/OpenList/v3 >=0; Go github.com/OpenListTeam/OpenList/v4 >=0 <4.2.4 (fixed))
- Verified: https://github.com/advisories/GHSA-86cx-wwf4-phq4 (GitHub-reviewed advisory GHSA-86cx-wwf4-phq4 lists affected ranges: Go github.com/OpenListTeam/OpenList/v4 >=0 <=4.2.3)

Commands are suggestions: review each one before running it.

Loading voting…