Skip to main content
VulnerabilityPublished

CVE-2026-69160: OpenListTeam OpenList · Insecure Direct Object Reference

Affects OpenListTeam OpenListSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.2.4 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.2.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade OpenList and openlistteam/OpenList to 4.2.4.

Affected software

ProductAffectedFixed in
OpenListTeamOpenListAffected
  • <4.2.4
Fixed in
  • 4.2.4
GitHubopenlistteam/OpenListpkg:github/openlistteam/OpenListOther threatsAffected
  • <4.2.4
Fixed in
  • 4.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OpenList to version 4.2.4 or later, where the issue is fixed. No other mitigation or temporary workaround is documented. Patch status is confirmed fixed in 4.2.4.

Description

OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a BasePath such as /base can submit a sibling path such as /base2/secret.txt, create a share for the out-of-scope file, and use the public share download or list handlers to read data outside the assigned directory. This issue is fixed in version 4.2.4.

References

Community reviews

Loading reviews…