How severe is GHSA-3jhm-87m6-x959?

No CVSS score has been assigned to GHSA-3jhm-87m6-x959 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3jhm-87m6-x959?

GHSA-3jhm-87m6-x959 affects the following packages: github.com/cloudflare/cfrpki (Go). Ecosystems affected: Go.

How do I fix GHSA-3jhm-87m6-x959?

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-3jhm-87m6-x959 is resolved across your whole dependency graph.

How do I detect GHSA-3jhm-87m6-x959 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cloudflare/cfrpki. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3jhm-87m6-x959 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-3jhm-87m6-x959?

O3 pinpoints whether GHSA-3jhm-87m6-x959 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3jhm-87m6-x959 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jhm-87m6-x959 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.

When was GHSA-3jhm-87m6-x959 published, and has it been updated?

GHSA-3jhm-87m6-x959 was published on June 25, 2022 and was last updated on February 4, 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

GHSA-3jhm-87m6-x959

Path traversal mitigation bypass in OctoRPKI

Also known asGO-2022-0496

Published

Jun 25, 2022

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

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

Impact

The existing URI path filters in OctoRPKI (version < 1.4.3) mitigating Path traversal vulnerability could be bypassed by an attacker. In case a malicious TAL file is parsed, it was possible to write files outside the base cache folder.

Specific Go Packages Affected

github.com/cloudflare/cfrpki/cmd/octorpki

Patches

The issue was fixed in version 1.4.3

References

CVE-2021-3907

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cloudflare/cfrpki`	all versions	1.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-3jhm-87m6-x959 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 pinpoints whether GHSA-3jhm-87m6-x959 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3jhm-87m6-x959. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The existing URI path filters in OctoRPKI (version < 1.4.3) mitigating Path traversal vulnerability could be bypassed by an attacker. In case a malicious TAL file is parsed, it was possible to write files outside the base cache folder. ### Specific Go Packages Affected github.com/cloudflare/cfrpki/cmd/octorpki ### Patches The issue was fixed in version 1.4.3 ### References [CVE-2021-3907](https://www.cvedetails.com/cve/CVE-2021-3907/)

O3 Security · Impact-Aware SCA

Is GHSA-3jhm-87m6-x959 in your dependencies?

O3 detects GHSA-3jhm-87m6-x959 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works