Gin Web Framework does not properly sanitize filename parameter of Context.FileAttachment function

Exploitation

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

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2023-29401: 0.48% estimated exploitation activity in the next 30 days; percentile 41.60 (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.

The filename parameter of the Context.FileAttachment function is not properly sanitized. A maliciously crafted filename can cause the Content-Disposition header to be sent with an unexpected filename value or otherwise modify the Content-Disposition header. For example, a filename of "setup.bat";x=.txt" will be sent as a file named "setup.bat". If the FileAttachment function is called with names provided by an untrusted source, this may permit an attacker to cause a file to be served with a name different than provided. Maliciously crafted attachment file name can modify the Content-Disposition header.

Published by the source

12 May 2023, 20:19 UTC

Last modified by the source

5 Nov 2023, 05:03 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2c4m-59x9-fr2g

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

# Patch Next advisory brief: CVE-2023-29401

Advisory: Gin Web Framework does not properly sanitize filename parameter of Context.FileAttachment function
IDs: CVE-2023-29401, GHSA-2c4m-59x9-fr2g
Record: https://patchnext.com/advisories/cve-2023-29401 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gin-gonic/gin 1.9.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gin-gonic/gin: affected >= 1.3.1-0.20190301021747-ccb9e902956d, < 1.9.1; fixed in 1.9.1

## Suggested inspection (read-only)
- Go github.com/gin-gonic/gin: 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/gin-gonic/gin.
- 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-2c4m-59x9-fr2g (GitHub-reviewed advisory GHSA-2c4m-59x9-fr2g lists affected ranges: Go github.com/gin-gonic/gin >=1.3.1-0.20190301021747-ccb9e902956d <1.9.1)

Commands are suggestions: review each one before running it.