GHSA-r67j-r569-jrwp — thrift
GHSA-r67j-r569-jrwp is a CWE-674 vulnerability in thrift. A fix is available for thrift — see the affected versions and patch details below.
Apache Thrift Node.js bindings vulnerable to Uncontrolled Recursion
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.
- 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 GHSA-r67j-r569-jrwp.
EPSS Exploitation Probability
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
thriftnpmDescription
Uncontrolled Recursion vulnerability in Apache Thrift Node.js bindings
This issue affects Apache Thrift: before 0.23.0.
Users are recommended to upgrade to version 0.23.0, which fixes the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | thrift | all versions | 0.23.0npm install thrift@0.23.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thrift, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update thrift to 0.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r67j-r569-jrwp 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-r67j-r569-jrwp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r67j-r569-jrwp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Multicluster Global Hub 1.3.4 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779212259 | RHSA-2026:22423 |
| Multicluster Global Hub 1.4.9 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779579439 | RHSA-2026:22347 |
| Multicluster Global Hub 1.6.5 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1780167118 | RHSA-2026:23345 |
| Red Hat Advanced Cluster Management for Kubernetes 2.15 | rhacm2/acm-grafana-rhel9:1780677003 | RHSA-2026:24539 |
| Red Hat multicluster global hub 1.5.3 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1778867753 | RHSA-2026:21769 |
Frequently Asked Questions
Is GHSA-r67j-r569-jrwp in your dependencies?
O3 Security finds GHSA-r67j-r569-jrwp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.