-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 0xCERT Security Advisory 0xCERT-2026-0356 ============================================================ Advisory-ID: 0xCERT-2026-0356 Severity: Medium Published: 2026-11-10T00:00:00.000Z Updated: 2026-11-16T00:50:07.725Z Chains: Bitcoin URL: https://www.0xcert.com/advisory/0xCERT-2026-0356 Title: Bitcoin Core before 28.3/29.2/30.0: inbound Tor peers wrongly receive -whitelist permissions Summary - ------- Bitcoin Core before 28.3, 29.2 and 30.0 grants -whitelist permissions to all inbound Tor peers when the local Tor daemon's IP falls in a whitelisted range, lifting DoS limits and privacy protections for untrusted peers. Thousands of mainnet nodes were affected. Upgrade. Details - ------- Summary Bitcoin Core disclosed CVE-2025-62860, rated Medium severity by the project. Inbound Tor peers appear with the IP address of the Tor daemon, usually on the same machine or local network. Affected versions whitelisted inbound Tor connections when the Tor proxy's address matched an IP range configured via -whitelist. Affected - - Bitcoin Core before 28.3, 29.2 and 30.0, only when the non-default -whitelist option is set to a range covering the Tor daemon - - Fixed in 28.3, 29.2 and 30.0 (PR #33395). Bitcoin Knots' maintainer was also notified, as were several affected software providers. Impact The -whitelist permissions lift various DoS limits and privacy-leak mitigations, so any inbound Tor peer was treated as trusted. According to the advisory, popular vendors bundled Bitcoin Core with a Tor daemon and set -whitelist to a matching range, which led to thousands of reachable mainnet nodes whitelisting all incoming Tor connections. The advisory does not report exploitation in the wild. Recommended actions - - Upgrade Bitcoin Core to a currently supported release (at minimum 28.3, 29.2 or 30.0). - - Node bundle vendors and operators: review -whitelist settings and avoid ranges that include the local Tor daemon. Source & attribution This 0xCERT advisory summarises the Bitcoin Core security disclosure published 10 November 2026, crediting Martin Zumsande and Antoine Poinsot for discovering and responsibly disclosing the issue: https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/. Details may change; refer to the original source for the authoritative record. References - ---------- - - https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/ - - CVE-2025-62860 - - https://bitcoincore.org/en/download/ Verify with the 0xCERT OpenPGP key: https://www.0xcert.com/pgp.asc Fingerprint: 5F94 3ED1 1E50 CF31 2128 C493 CCC7 D9EC 9415 723D -----BEGIN PGP SIGNATURE----- wrsEARYKAG0Fgmr+AsoJEDe9Tbcr+ZxrRRQAAAAAABwAIHNhbHRAbm90YXRp b25zLm9wZW5wZ3Bqcy5vcmeSuS5Toq0nRuzWBBkDtWxwO76Ni9oIticn8Ef8 z3StVBYhBGCkkFZbJcT5QWu27ze9Tbcr+ZxrAABgtgD/cMbWkpIHLpZEQ+ot X+JzyFG5izkT4fMFAbv1S7MMdaQBAJDgQvxftblSneSytPE6goneHBj1YtW8 agC1KBfPx0QO =pw+j -----END PGP SIGNATURE-----