Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7

goshs is Missing Write Protection for Parametric Data Values

CVE-2026-40188GHSA-2943-crp8-38xx

What to do

Vendor response not established. 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/patrickhener/goshs

    Affected
    >= 1.0.7, <= 1.1.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS
  • CVE-2026-40188: 0.32% estimated exploitation activity in the next 30 days; percentile 24.81 (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 SFTP command rename sanitizes only the source path and not the destination, so it is possible to write outside of the root directory of the SFTP. Details Here is the issue: PoC To exploit just upload a file on the SFTP and rename it to a file with full path. Currently no key.txt file inside /tmp Start the SFTP server: Connect to the SFTP and uploading the file: The file is stored properly. goshs log: Rename command with full path: goshs log: Key file is now in /tmp Impact This allows file write and can be used either for an RCE in form of overwrite an SSH key, or by overwriting a configuration etc.

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

    Published from ghsa record GHSA-2943-crp8-38xx

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

Advisory: goshs is Missing Write Protection for Parametric Data Values
IDs: CVE-2026-40188, GHSA-2943-crp8-38xx
Record: https://patchnext.com/advisories/cve-2026-40188 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/patrickhener/goshs: affected >= 1.0.7, <= 1.1.4

## Suggested inspection (read-only)
- Go github.com/patrickhener/goshs: 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/patrickhener/goshs.
- 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-2943-crp8-38xx (GitHub-reviewed advisory GHSA-2943-crp8-38xx lists affected ranges: Go github.com/patrickhener/goshs >=1.0.7 <=1.1.4)

Commands are suggestions: review each one before running it.

Loading voting…