Chia Blockchain vulnerabilities
🔔 Create alert RSS Version checker
Published CVEs affecting Chia Blockchain: 3 record(s), with affected versions and fixes.cpe:2.3:a:chia:blockchain
CVE-2026-3194
High · 7.0
CWE-306 Feb 25, 2026
Chia Blockchain RPC Server Master Passphrase get_private_key missing authentication
A flaw has been found in Chia Blockchain 2.1.0. The affected element is the function send_transaction/get_private_key of the component RPC Server Master Passphrase Handler. This manipulation causes missing authentication. The attack can only be executed locally. The attack's complexity is rated as high. The exploitability is described as difficult. The exploit has been published and may be used. The vendor was informed early via email. A separate report via bugbounty was rejected with the reason "This is by design. The user is responsible for host security".
CVE-2026-3193
Low · 3.1
CWE-352 Feb 25, 2026
Chia Blockchain send_transaction cross-site request forgery
A vulnerability was detected in Chia Blockchain 2.1.0. Impacted is an unknown function of the file /send_transaction. The manipulation results in cross-site request forgery. The attack may be performed from remote. The attack requires a high level of complexity. The exploitability is considered difficult. The exploit is now public and may be used. The vendor was informed early via email. A separate report via bugbounty was rejected with the reason "This is by design. The user is responsible for host security".
CVE-2026-3192
High · 8.1
CWE-306 Feb 25, 2026
Chia Blockchain RPC Credential rpc_server_base.py _authenticate improper authentication
A security vulnerability has been detected in Chia Blockchain 2.1.0. This issue affects the function _authenticate of the file rpc_server_base.py of the component RPC Credential Handler. The manipulation leads to improper authentication. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitability is assessed as difficult. The exploit has been disclosed publicly and may be used. The vendor was informed early via email. A separate report via bugbounty was rejected with the reason "This is by design. The user is responsible for host security".