# CVE-2026-10031: SFTPGo < 2.7.4 Permission Bypass via Symbolic Link Creation

> Authenticated users can bypass directory access controls via symbolic links to read or modify restricted files in SFTPGo.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-3964-29ff-vwff, GHSA-fj9v-mxr3-w75w

## What is CVE-2026-10031?

CVE-2026-10031 is a medium-severity missing authorization vulnerability in drakkan SFTPGo, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SFTPGo prior to 2.7.4 contains a permission bypass vulnerability that allows authenticated users to circumvent per-directory access controls by creating symbolic links in a permitted directory that point to files in directories where download, upload, or overwrite permissions are denied. Attackers can exploit the create_symlinks permission combined with read and write access in one directory to read or modify files in restricted directories, as operations are authorized against the link's directory permissions rather than the dereferenced target's directory permissions.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-10031?


## How do I fix CVE-2026-10031?

No fix has been published for CVE-2026-10031 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10031 being exploited?

There is no known exploitation of CVE-2026-10031 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10031 and fix it if it is affected.

What it is: CVE-2026-10031 is a medium-severity missing authorization vulnerability in drakkan SFTPGo, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10031 in the wild and no public exploit code.

Affected product: drakkan SFTPGo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10031/ (Markdown: https://insights.sbomify.com/CVE-2026-10031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10031
- OSV: https://osv.dev/vulnerability/CVE-2026-10031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10031/
Summaries are generated and may contain mistakes; the official description above is the record.