Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.6amended

OpenList: Authenticated users can rename files outside their base path via batch rename src_name traversal

CVE-2026-73509GHSA-95cv-r8x4-vh75

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
7.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
EPSS
  • CVE-2026-73509: 0.52% estimated exploitation activity in the next 30 days; percentile 44.35 (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 The /api/fs/batchrename handler validates and authorizes only the requested source directory. It rejects path separators in newname, but it does not validate srcname. The handler concatenates srcdir and attacker-controlled srcname, then passes the result to the filesystem rename layer, where the path is normalized. An authenticated user with rename permission can set srcname to traversal segments such as ../../ab/secret.txt. When the user's base path is /team/a and srcdir is /writable, the authorized directory becomes /team/a/writable, but the final source path normalizes to /team/ab/secret.txt. The file outside the user's base path is then renamed. Details The HTTP API registers filesystem management routes under the authenticated group: - server/router.go:104 registers fs(auth.Group("/fs")). - server/router.go:198 through server/router.go:205 expose /api/fs/batchrename. The vulnerable code is in server/handles/fsbatch.go: - srcdir is constrained through…

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

    Amended from ghsa record GHSA-95cv-r8x4-vh75

  2. Revision 1 · created ·

    Published from osv record GO-2026-6110

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-73509

Advisory: OpenList: Authenticated users can rename files outside their base path via batch rename `src_name` traversal
IDs: CVE-2026-73509, GHSA-95cv-r8x4-vh75
Record: https://patchnext.com/advisories/cve-2026-73509 (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: High (CVSS 7.6)
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-6110 (OSV record GO-2026-6110 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-95cv-r8x4-vh75 (GitHub-reviewed advisory GHSA-95cv-r8x4-vh75 lists affected ranges: Go github.com/OpenListTeam/OpenList/v4 >=0 <=4.2.3)

Commands are suggestions: review each one before running it.

Loading voting…