GHSA-q66h-m87m-j2q6
Bitcoinrb Vulnerable to Command injection via RPC
GHSA-q66h-m87m-j2q6 is a low vulnerability (CVSS 2.0) in bitcoinrb, published February 10, 2026. No source lists public exploit code. Fixed in bitcoinrb 1.12.0.
- Severity
- 2.0 LowCVSS 4.0, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
1.12.0bitcoinrb +1 more
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Affected packages
| Package | Affected | Fixed |
|---|---|---|
bitcoinrbRubyGems | before 1.12.0 | 1.12.0 |
bitcoinrbRubyGems | before 1.12.0, plus listed versions 0.0.10.1.10.1.20.1.30.1.4 Show 40 moreShow less0.1.50.1.60.1.70.1.80.1.90.2.00.2.10.2.20.2.40.2.50.2.60.2.70.2.80.2.90.3.00.3.10.3.20.4.00.5.00.6.00.7.00.8.00.9.01.0.01.1.01.1.11.10.01.11.01.2.01.2.11.3.01.4.01.5.01.6.01.7.01.8.01.8.11.8.21.9.01.9.1 | 1.12.0 |
What each source reports
GitHub Advisories Score used
Bitcoinrb Vulnerable to Command injection via RPC
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.
- Record
GHSA-q66h-m87m-j2q6- CVSS 4.0
- 2.0 Low
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P - Weakness
- CWE-77
- Updated
- 2026-11-02
OSV
Bitcoinrb Vulnerable to Command injection via RPC
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.
- Record
GHSA-q66h-m87m-j2q6- CVSS 4.0
- 2.0 Low
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P - Weakness
- CWE-77
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.