How severe is GHSA-jphm-g89m-v42p?

No CVSS score has been assigned to GHSA-jphm-g89m-v42p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jphm-g89m-v42p?

GHSA-jphm-g89m-v42p affects the following packages: github.com/cortexproject/cortex (Go). Ecosystems affected: Go.

How do I fix GHSA-jphm-g89m-v42p?

No patched version of github.com/cortexproject/cortex has shipped for GHSA-jphm-g89m-v42p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-jphm-g89m-v42p in my Go dependencies?

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

How do I mitigate GHSA-jphm-g89m-v42p 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 GHSA-jphm-g89m-v42p actively exploited in the wild?

No public exploit code has been indexed for GHSA-jphm-g89m-v42p 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 GHSA-jphm-g89m-v42p?

GHSA-jphm-g89m-v42p has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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 GHSA-jphm-g89m-v42p?

GHSA-jphm-g89m-v42p 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 GHSA-jphm-g89m-v42p published, and has it been updated?

GHSA-jphm-g89m-v42p was published on September 2, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Path traversal in Grafana Cortex

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐹github.com/cortexproject/cortex

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

An issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.)

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cortexproject/cortex`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

cortexlinuxfoundation

≤ 1.9.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/cortexproject/cortex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/cortexproject/cortex has shipped for GHSA-jphm-g89m-v42p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 HatModerate

CVE-2021-36157 refers to a directory traversal issue in Grafana Cortex, which is neither shipped in Red Hat Enterprise Linux, nor it has any dependency with Grafana package, hence, not-affected.

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 4.13	`openshift4/ose-cluster-storage-operator:v4.13.0-202305181415.p0.g6479617.assembly.stream`	RHSA-2023:3304
Red Hat OpenShift Container Platform 4.14	`openshift4/ose-cluster-storage-operator:v4.14.0-202310201027.p0.gdbb1514.assembly.stream`	RHSA-2023:5006

Frequently Asked Questions

An issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.)

O3 Security · Impact-Aware SCA

Is GHSA-jphm-g89m-v42p in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

Path traversal in Grafana CortexGHSA-jphm-g89m-v42p