Skip to content

← Actionable
High, CVSS 7.5

Gogs Directory Traversal

CVE-2018-20303GHSA-9hxg-w7qf-hh93

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gogs.io/gogs 0.11.80-0.20181218063808-ff93d9dbda5c), redeploy, then verify what is actually installed.

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.

Affected packages

  • Go gogs.io/gogs

    Affected
    < 0.11.80-0.20181218063808-ff93d9dbda5c
    Fixed in
    0.11.80-0.20181218063808-ff93d9dbda5c

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2018-20303: 3.29% estimated exploitation activity in the next 30 days; percentile 88.50 (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.

In pkg/tool/path.go in Gogs before 0.11.82.1218, a directory traversal in the file-upload functionality can allow an attacker to create a file under data/sessions on the server, a similar issue to CVE-2018-18925.

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

    Published from ghsa record GHSA-9hxg-w7qf-hh93

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-2018-20303

Advisory: Gogs Directory Traversal
IDs: CVE-2018-20303, GHSA-9hxg-w7qf-hh93
Record: https://patchnext.com/advisories/cve-2018-20303 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gogs.io/gogs 0.11.80-0.20181218063808-ff93d9dbda5c. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go gogs.io/gogs: affected < 0.11.80-0.20181218063808-ff93d9dbda5c; fixed in 0.11.80-0.20181218063808-ff93d9dbda5c

## Suggested inspection (read-only)
- Go gogs.io/gogs: 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 gogs.io/gogs.
- 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-9hxg-w7qf-hh93 (GitHub-reviewed advisory GHSA-9hxg-w7qf-hh93 lists affected ranges: Go gogs.io/gogs >=0 <0.11.80-0.20181218063808-ff93d9dbda5c)

Commands are suggestions: review each one before running it.

Loading voting…