How severe is CVE-2023-49569?

CVE-2023-49569 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-49569?

CVE-2023-49569 affects the following packages: github.com/go-git/go-git/v5 (Go), gopkg.in/src-d/go-git.v4 (Go). Ecosystems affected: Go.

How do I fix CVE-2023-49569?

Update github.com/go-git/go-git/v5 to 5.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49569 is resolved across your whole dependency graph.

How do I detect CVE-2023-49569 in my Go dependencies?

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

How do I mitigate CVE-2023-49569 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2023-49569 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-49569 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-49569?

CVE-2023-49569 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-49569?

CVE-2023-49569 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-49569 published, and has it been updated?

CVE-2023-49569 was published on January 12, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

CVE-2023-49569 — go-git

CRITICAL

CVE-2023-49569 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in github.com/go-git/go-git/v5. A fix is available for github.com/go-git/go-git/v5 — see the affected versions and patch details below.

Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients

Also known asGHSA-449p-3h89-pw88GO-2024-2456

Published

Jan 12, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

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

2 pkgs affected

🐹github.com/go-git/go-git/v5🐹gopkg.in/src-d/go-git.v4

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

Impact

A path traversal vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved.

Applications are only affected if they are using the ChrootOS, which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS or in-memory filesystems are not affected by this issue. This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible in a timely manner, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/go-git/go-git/v5`	≥ 5.0.0&&< 5.11.0	5.11.0`go get github.com/go-git/go-git/v5@v5.11.0`
🐹Go	`gopkg.in/src-d/go-git.v4`	≥ 4.0.0	No fix

Affected Products

1 product · 1 configurations

Application

go-gitgo-git_project

≥ 4.0.0 && < 5.11.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-git/go-git/v5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/go-git/go-git/v5 to 5.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49569 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 HatCritical

This problem only affects the go implementation and not the original git cli code. Applications using BoundOS or in-memory filesystems are not affected by this issue. Clients should be limited to connect to only trusted git servers to reduce the risk of compromise. In OpenShift Container Platform (OCP) the vulnerable…

Workaround published by Red Hat

In cases where a bump to the latest version of go-git is not possible, a recommendation to reduce the exposure of this threat is limiting its use to only trust-worthy Git servers.

Source: Red Hat security advisory for CVE-2023-49569 (CC BY 4.0)

Product	Fixed in	Advisory
Builds for Red Hat OpenShift	`openshift-builds-controller-container`	RHSA-2024:6221
multicluster-globalhub 1.0 for RHEL 8	`multicluster-globalhub/multicluster-globalhub-grafana-rhel8:v1.0.2-4`	RHSA-2024:0989
OPENSHIFT-BUILDS-1.0-RHEL-8	`openshift-builds/openshift-builds-controller-rhel8:v1.0.1-4`	RHSA-2024:1557
Openshift Serverless 1 on RHEL 8	`openshift-serverless-clients-0:1.10.0-6.el8`	RHSA-2024:0880
Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8	`rhacm2/multicluster-operators-subscription-rhel8:v2.9.2-2`	RHSA-2024:0298
Red Hat Advanced Cluster Security 4.3	`advanced-cluster-security/rhacs-central-db-rhel8:4.3.6-2`	RHSA-2024:1549
Red Hat Ceph Storage 5.3	`ceph-2:16.2.10-266.el8cp`	RHSA-2024:4118
Red Hat Ceph Storage 6.1	`rhceph/keepalived-rhel9:2.2.8-11`	RHSA-2024:2633

Frequently Asked Questions

### Impact A path traversal vulnerability was discovered in go-git versions prior to `v5.11`. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved. Applications are only affected if they are using the [ChrootOS](https://pkg.go.dev/github.com/go-git/go-billy/v5/osfs#ChrootOS), which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using [BoundOS](https://pkg.go.dev/github.com/go-git/go-billy/v5/osfs#BoundOS) or in-memory filesystems are not aff