Symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations in dbdeployer

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N

EPSS

• CVE-2020-26277: 1.20% estimated exploitation activity in the next 30 days; percentile 68.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Users unpacking a tarball through dbdeployer may use a maliciously packaged tarball that contains symlinks to files external to the target. In such scenario, an attacker could induce dbdeployer to write into a system file, thus altering the computer defences. Mitigating factors For the attach to succeed, the following factors need to contribute: The user is logged in as root. While dbdeployer is usable as root, it was designed to run as unprivileged user. The user has taken a tarball from a non secure source, without testing the checksum. When the tarball is retrieved through dbdeployer, the checksum is compared before attempting to unpack. Analysis An attacker could inject a symbolic link into the tarball, so that a file could result into fakefile - /etc/passwd or some equally important file. As it is now, dbdeployer would create the symlink as defined, with a local file fakefile linked to /etc/passwd. The danger here is that any process with the privileges to write to both…

Published by the source

12 Feb 2022, 00:14 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-47wr-426j-fr82

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

# Patch Next advisory brief: CVE-2020-26277

Advisory: Symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations in dbdeployer
IDs: CVE-2020-26277, GHSA-47wr-426j-fr82
Record: https://patchnext.com/advisories/cve-2020-26277 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/datacharmer/dbdeployer 1.58.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/datacharmer/dbdeployer: affected < 1.58.2; fixed in 1.58.2

## Suggested inspection (read-only)
- Go github.com/datacharmer/dbdeployer: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/datacharmer/dbdeployer.
- 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://github.com/advisories/GHSA-47wr-426j-fr82 (GitHub-reviewed advisory GHSA-47wr-426j-fr82 lists affected ranges: Go github.com/datacharmer/dbdeployer >=0 <1.58.2)

Commands are suggestions: review each one before running it.