How severe is GHSA-8459-6rc9-8vf8?

No CVSS score has been assigned to GHSA-8459-6rc9-8vf8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8459-6rc9-8vf8?

GHSA-8459-6rc9-8vf8 affects the following packages: github.com/cloudflare/cfrpki (Go). Ecosystems affected: Go.

How do I fix GHSA-8459-6rc9-8vf8?

Update github.com/cloudflare/cfrpki to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8459-6rc9-8vf8 is resolved across your whole dependency graph.

How do I detect GHSA-8459-6rc9-8vf8 in my Go dependencies?

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

How do I mitigate GHSA-8459-6rc9-8vf8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8459-6rc9-8vf8?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8459-6rc9-8vf8 can be triaged on real exposure rather than presence alone.

Is GHSA-8459-6rc9-8vf8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8459-6rc9-8vf8 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-8459-6rc9-8vf8?

GHSA-8459-6rc9-8vf8 has an EPSS (Exploit Prediction Scoring System) score of 4.2%, placing it in the 91th 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-8459-6rc9-8vf8?

GHSA-8459-6rc9-8vf8 is classified as Improper Input Validation (CWE-20), Path Traversal (CWE-22). These weakness types 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-8459-6rc9-8vf8 published, and has it been updated?

GHSA-8459-6rc9-8vf8 was published on February 14, 2022 and was last updated on January 14, 2025. 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

GHSA-8459-6rc9-8vf8 — cfrpki

Fix: cloudflare/cfrpki@a053a80

GHSA-8459-6rc9-8vf8 is a Improper Input Validation vulnerability in github.com/cloudflare/cfrpki. A fix is available for github.com/cloudflare/cfrpki — see the affected versions and patch details below.

Path traversal in github.com/cloudflare/cfrpki/cmd/octorpki

Also known asCVE-2021-3907 GHSA-cqh2-vc2f-q4fhGO-2022-0248

Published

Feb 14, 2022

Updated

Jan 14, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/cloudflare/cfrpki

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

OctoRPKI does not escape a URI with a filename containing "..", this allows a repository to create a file, (ex. rsync://example.org/repo/../../etc/cron.daily/evil.roa), which would then be written to disk outside the base cache folder. This could allow for remote code execution on the host machine OctoRPKI is running on.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cloudflare/cfrpki`	all versions	1.4.3`go get github.com/cloudflare/cfrpki@v1.4.3`

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/cloudflare/cfrpki, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cloudflare/cfrpki to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8459-6rc9-8vf8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8459-6rc9-8vf8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8459-6rc9-8vf8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In the case that a malicious TAL file is parsed pointing to a repository that provides a malicious ROA file which octorpki downloads, it is possible to bypass the current directory traversal mitigation to allow writing outside of the current directory. ### Patches No patch release has been made

O3 Security · Impact-Aware SCA

Is GHSA-8459-6rc9-8vf8 in your dependencies?

O3 Security finds GHSA-8459-6rc9-8vf8 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works