How severe is GHSA-q66h-m87m-j2q6?

No CVSS score has been assigned to GHSA-q66h-m87m-j2q6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q66h-m87m-j2q6?

GHSA-q66h-m87m-j2q6 affects the following packages: bitcoinrb (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-q66h-m87m-j2q6?

Update bitcoinrb to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q66h-m87m-j2q6 is resolved across your whole dependency graph.

How do I detect GHSA-q66h-m87m-j2q6 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bitcoinrb. 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-q66h-m87m-j2q6 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-q66h-m87m-j2q6?

O3 pinpoints whether GHSA-q66h-m87m-j2q6 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-q66h-m87m-j2q6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q66h-m87m-j2q6 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-q66h-m87m-j2q6 published, and has it been updated?

GHSA-q66h-m87m-j2q6 was published on February 10, 2026 and was last updated on February 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

GHSA-q66h-m87m-j2q6

Bitcoinrb Vulnerable to Command injection via RPC

Published

Feb 10, 2026

Updated

Feb 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

💎bitcoinrb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Summary: Remote Code Execution

Unsafe handling of request parameters in the RPC HTTP server results in command injection

Details

In lib/bitcoin/rpc/http_server.rb line 30-39, the JSON body of a POST request is parsed into command and args variables. These values are then passed to send, which is used to call an arbitrary class method. However, there is no validation that the provided command value is one of the expected RPC methods. This means that an attacker could supply a command value such as system, and then pass arbitrary system commands into the args parameter and achieve remote code execution.

PoC

Start the RPC server
Send a request to the RPC server as so:

curl -X POST http://127.0.0.1:18443 -H 'Content-Type: application/json' \
   -d '{"method":"eval","params":["File.write(\"/tmp/pwned\",\"owned\")"]}'

Check the /tmp folder on the machine where the RPC server is being run. If a folder /pwned now exists, the vulnerability is confirmed.

Impact

This vulnerability would impact anyone running the RPC server. The impact is higher for those who are running it publicly exposed to the internet.

Remediation

Mitigating Factors:

The RPC server is part of the experimental SPV node feature, which is not documented and has very few users.
The SPV-related features may be removed in future releases.

Resolution:

Added whitelist validation to allow only RPC methods defined in RequestHandler.
Fixed in version 1.12.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`bitcoinrb`	all versions	1.12.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bitcoinrb. 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 bitcoinrb to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q66h-m87m-j2q6 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-q66h-m87m-j2q6 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-q66h-m87m-j2q6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary: Remote Code Execution Unsafe handling of request parameters in the RPC HTTP server results in command injection ### Details In lib/bitcoin/rpc/http_server.rb line 30-39, the JSON body of a POST request is parsed into `command` and `args` variables. These values are then passed to `send`, which is used to call an arbitrary class method. However, there is no validation that the provided `command` value is one of the expected RPC methods. This means that an attacker could supply a `command` value such as `system`, and then pass arbitrary system commands into the `args` parameter an

O3 Security · Impact-Aware SCA

Is GHSA-q66h-m87m-j2q6 in your dependencies?

O3 detects GHSA-q66h-m87m-j2q6 across RubyGems 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