monero.loveA little love for the network.
← All news

Monero / Ops Brief / RPC

Monero Node Ops Brief: November 20, 2026

Monero public-node updates: ZMQ exposure guidance, HTTP-header parsing review, and proposed Tor/I2P relay and proxy-DNS changes.

An open field notebook and pencil beside a server, in a paper collage.

This week's Monero proposals cover warnings against public ZMQ exposure, a reported HTTP-header parsing weakness, and Tor/I2P relay privacy. All remain open pull requests as of November 20. None is a newly released production fix.

Coverage: November 13 to 20, 2026 (UTC).

Review ZMQ exposure now

Urgency: high if reachable by untrusted clients. Affected: monerod ZMQ RPC/PUB and P2Pool integrations.

On November 18, Monero maintainer selsta proposed startup warnings and documentation explaining that exposing ZMQ RPC or PUB endpoints to untrusted clients is unsafe. The warning also applies when --restricted-zmq-rpc is enabled: restricting methods does not make an endpoint suitable for public access. The patch remains open. It does not automatically secure an existing deployment.

Action: Inspect listening addresses and network reachability. Keep ZMQ on loopback where possible, or limit it to explicitly trusted clients. When changing access, verify that P2Pool still receives block notifications and reconnects after a daemon restart. Watch notification gaps and mining-template freshness.

This is explicit upstream safety guidance, not a newly announced CVE or evidence of active exploitation. Treat public daemon HTTP RPC and trusted ZMQ notification access as separate interfaces.

Sources: PR #11766: opened November 18, 2026, proposed documentation and code.

Review wildcard CORS and malformed-header handling

Urgency: medium for exposed RPC using wildcard CORS. Affected: monerod and monero-wallet-rpc HTTP parsing.

A contributor's November 17 report demonstrates a bare carriage return in an Origin header being reflected into a malformed response header when wildcard CORS is enabled. A downstream parser that accepts that character as a line break could interpret an injected header. The proposed change rejects control characters other than horizontal tabs in header values. The shared client parser would also benefit.

The report includes a reproduction and tests, but does not establish an exploited production chain. The patch remains open. On November 19, selsta questioned its value given an upcoming Boost.Beast migration. That comment is not evidence that a replacement parser has reached a release.

Action: Review whether wildcard CORS is necessary and prefer explicit allowed origins where practical. Reject malformed headers at HTTP ingress. Test browser-wallet compatibility after policy changes. Do not expose wallet-management RPC as a public-node service or deploy a review branch as a security update.

Source: PR #11760: opened November 17, maintainer response November 19, 2026.

Server symbols linked across layered paper mountains with orange connecting lines.

Track Tor/I2P relay and proxy-DNS changes together

Urgency: review before a future upgrade. Do not deploy a review branch. Affected: monerod anonymity-network peering and transaction relay.

  • PR #11743: opened November 13, 2026 proposes inbound-only acceptance of Tor/I2P transaction messages and uniform delayed forwarding into public-network relay. It prevents the sender's fluff flag from bypassing the delay. The intended privacy improvement is a design goal, not a demonstrated anonymity guarantee or a report of active deanonymization.
  • PR #11723: revised November 18 to 19, 2026, originally opened November 10, now skips hostname peers with a warning when proxy settings disable local DNS. Configured peers and fallback seeds use the same check. Online startup fails if every configured exclusive peer is skipped. Offline startup remains possible.

Action: Inventory hostname-based priority, exclusive and seed peers before testing a release containing these changes. Canary-test startup, resolver activity, peer connectivity and transaction propagation through the intended proxy path. Both proposals remain under review and carry a needs-backport label. Neither is a released fix. The November 13 brief covers the earlier proxy-DNS proposal.

Production and release position

For FreeBSD and Linux operators alike, these are application-level reviews, not a reason to install master. Retain a copy of the current binary and configuration before testing future tagged releases. No new capacity gain or platform-specific compatibility claim is established by these proposals.

No new production release was found this week for Monero, P2Pool, XMRig or XMRig-Proxy. Their stable versions remain Monero 0.18.5.4, P2Pool 4.18.1 and XMRig/XMRig-Proxy 6.26.0. Generic infrastructure updates are outside this brief.

Support Monero Love

Help keep the public nodes and packages running. Send any amount of XMR.

Scan with a Monero wallet to donate to Monero Love.89hGTKxRVA3AUeKAbCRBt5TMSzq3MQZooNNsezCpNFjp2oeJPRx8AJeGKA8ziHZNqab78f4Vr1ntxhPDxX5298nnGZjHkhm