NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2023-26125 — gin

MEDIUMFix: gin-gonic/gin#3500

CVE-2023-26125 is a medium-severity (CVSS 5.6) Improper Input Validation vulnerability in github.com/gin-gonic/gin. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/gin-gonic/gin — see the affected versions and patch details below.

Improper input validation in github.com/gin-gonic/gin

Also known asGHSA-3vp4-m3rf-835h
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-26125.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.94%1.41%0.2%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/gin-gonic/gin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Versions of the package github.com/gin-gonic/gin before version 1.9.0 are vulnerable to Improper Input Validation by allowing an attacker to use a specially crafted request via the X-Forwarded-Prefix header, potentially leading to cache poisoning.

Note: Although this issue does not pose a significant threat on its own it can serve as an input vector for other more impactful vulnerabilities. However, successful exploitation may depend on the server configuration and whether the header is used in the application logic.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/gin-gonic/ginall versions1.9.0go get github.com/gin-gonic/gin@v1.9.0

Affected Products

1 product · 1 configurations
Application
gingin-gonic
< 1.9.0
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Versions of the package github.com/gin-gonic/gin before 1.9.0 are vulner…

github.comNVDMay 2023

Report on security.snyk.io

security.snyk.ioNVDMay 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gin-gonic/gin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/gin-gonic/gin to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26125 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2023-26125 (CC BY 4.0)
ProductFixed inAdvisory
Migration Toolkit for Virtualization 2.5migration-toolkit-virtualization/mtv-controller-rhel9:2.5.2-5RHBA-2023:6078
MTA-6.2-RHEL-9mta/mta-hub-rhel9:6.2.0-16RHSA-2023:4627
Red Hat Migration Toolkit for Containers 1.7rhmtc/openshift-migration-controller-rhel8:v1.7.11-4RHSA-2023:4293
Red Hat OpenShift Container Platform 4.13openshift4/ose-agent-installer-csr-approver-rhel8:v4.13.0-202411300029.p0.g19034d8.assembly.stream.el8RHSA-2024:10813
Red Hat OpenShift Container Platform 4.13openshift4/ose-agent-installer-api-server-rhel8:v4.13.0-202410242307.p0.gec6e27b.assembly.stream.el8RHSA-2024:8688

Frequently Asked Questions

Versions of the package github.com/gin-gonic/gin before version 1.9.0 are vulnerable to Improper Input Validation by allowing an attacker to use a specially crafted request via the X-Forwarded-Prefix header, potentially leading to cache poisoning. **Note:** Although this issue does not pose a significant threat on its own it can serve as an input vector for other more impactful vulnerabilities. However, successful exploitation may depend on the server configuration and whether the header is used in the application logic.
O3 Security · Impact-Aware SCA

Is CVE-2023-26125 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-26125: gin — Fixed in 1.9.0