Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
53/100 average clarity
22Strong · 80–100
158Adequate · 60–79
690Thin · 40–59
66Opaque · 0–39
14security candidates with opaque commit messaging
This commit only adds a new automated test tool (a fuzzer) for the Monero wallet. It does not change any production wallet, node, or consensus code. It cannot by itself introduce a vulnerability that affects real users, nor does it fix one…
This is a cleanup and refactoring patch for Monero's new FCMP++ (full-chain membership proof) database and transaction handling code. It renames a method, fixes typos and comments, tightens a constant name, adds a safety check that outputs…
Added runtime invariant check that locked outputs do not unlock below the default unlock blockRefactored transparent-amount commitment collection to reduce indirection and potential misuseClarified unlock-time semantics and coinbase detection in migration code
This commit is a cleanup and hardening patch following an earlier pull request. It adds a safety check to make sure outputs are not incorrectly treated as spendable before they should be, fixes several typos and variable-name issues, rewri…
Added invariant check that outputs unlock no earlier than the default unlock block before adding locked outputs to the databaseRefactored transparent-amount commitment collection to remove std::reference_wrapper indirection, reducing complexityCorrected constant-name typos in spendable-age calculations
This is a one-line fix in Monero's wallet software that adjusts how far ahead the wallet tries to 'skip' scanning after a blockchain reorganization (reorg). A reorg happens when the network briefly disagrees on the chain of blocks and then…
Incorrect scan resume height after blockchain reorgPotential missed transaction detectionBalance accuracy issue in wallet
This commit is a code cleanup that replaces the non-standard WIN32 preprocessor macro with the compiler-defined _WIN32 macro across 18 files. It does not change program logic or behavior; it only makes Windows-specific code detection more …
No functional code changes observedPreprocessor macro standardization onlyWindows-specific code paths remain identical in behavior
This commit only adds a new automated security test (a fuzzer) for Monero's wallet cache file parser. It does not change any production wallet code, fix a bug, or introduce a vulnerability. It is a testing-only addition intended to help fi…
Adds a fuzz target for wallet cache deserializationNo changes to production code pathsNo patch of a reported vulnerability
This Monero update adds a cache that remembers which transactions in the memory pool have already failed expensive input verification, so the node does not waste CPU re-checking the same bad transaction repeatedly. It is a performance and …
Adds caching of invalid input verification IDs to avoid repeated expensive ring signature verificationReduces CPU consumption for transactions that re-enter or remain in the mempool with unchanged invalid inputsCould mitigate a minor denial-of-service vector where a node repeatedly re-verifies a bad transaction
This patch changes how Monero's daemon calculates the total coinbase transaction sum (emission plus fees) for a range of blocks. Previously, the code called a general 'get_transactions' helper that could trigger a deadlock because it might…
Deadlock avoidance in consensus-related coinbase emission calculationChange from general transaction retrieval to direct, pruned database readAddition of functional test covering coinbase sum correctness
This change is a performance optimization for the Monero wallet's balance-reporting RPC. When a user asks for balances across many subaddresses, the code now pre-counts unspent outputs in one pass instead of re-scanning the entire transact…
This update adds a safety check in the Monero wallet's fast refresh process. Previously, if a malicious or buggy remote server told the wallet to start syncing from a block height beyond the wallet's known blockchain data, the wallet could…
Added bounds check on untrusted server-supplied start_height against local hash chain sizeDefensive hardening at wallet/daemon trust boundaryUnit test demonstrates rejection of out-of-bounds refresh request
This commit tightens filename validation in the Monero wallet's remote-control interface (RPC server). It now rejects wallet names that are just '.' or '..', contain a hidden null character, or contain path separators like '/' (and on Wind…
Path-traversal defense: blocks directory separators and parent-directory references in wallet filenamesNull-byte injection defense: rejects embedded NUL characters that could truncate or confuse downstream path handlingRPC input validation hardening in wallet_rpc_server
This Monero wallet update fixes a file-handling bug in the 'save wallet as' function. Previously, the code compared only the main wallet cache path and used a simple path check that could be fooled by symlinks or filenames ending in '.keys…
Path overlap / self-overwrite protection for wallet cache and keys filesSymlink and hardlink alias detection using boost::filesystem::equivalentRejection of ambiguous paths where .keys file and cache file could collide
This commit adds an optional, faster way to set up N-of-N Monero multisig wallets. Normally, all signers must complete a final verification round to prove they are active and have finished setup. The new 'fast non-interactive setup' skips …
New feature adds a non-default, opt-in fast setup path that intentionally weakens a liveness/verification guaranteeForce-update flag (force_update_use_with_caution) is used internally to bypass the normal post-KEX roundUser-facing and API documentation clearly warn that funds may become inaccessible if other signers do not complete setup
This change refactors how Monero's wallet fetches transaction data when creating or verifying 'spend proofs'—cryptographic receipts that prove you spent funds. Previously, spend-proof code fetched transactions directly from the network dae…
Refactoring of spend-proof transaction lookup to a single helperAddition of explicit RPC timeout parameter to transaction fetch helperImproved daemon RPC error/status reporting in get_tx_for_proof
This commit refactors how the Monero wallet fetches a transaction when verifying a payment proof (the check_tx_key feature). It replaces a direct daemon RPC call with a helper function called get_tx_for_proof, which is described in the com…
Replaces direct /gettransactions RPC with centralized helper for proof verificationCommit title explicitly frames change as 'verify v1 txid in check_tx_key'Removes local tx_hash == txid equality check in favor of helper-internal verification
This change stops a Monero wallet from creating 'InProofs' (receipt proofs) for transactions that the wallet itself sent. InProofs are meant to prove to someone else that you received money. If a wallet could generate an InProof for a tran…
Prevents generation of misleading InProofs for outgoing/self-sent transactionsAdds explicit runtime guard in wallet proof generation pathFunctional tests updated to assert refusal behavior
This patch fixes a bug in the Monero wallet where, if a pending transaction failed, the wallet could incorrectly mark coins as unspent even though they had already been spent by a separate confirmed transaction. This could let the wallet t…
Incorrect state reset on failure pathPotential double-spend attempt caused by stale UTXO selectionWallet balance/availability inconsistency after failed pending tx
This commit only adds a new automated fuzz-testing harness for Monero wallet features. It does not change any production wallet code, fix a bug, or alter network behavior. It is a test-only addition intended to help find bugs in the future…
Adds fuzz targets for payment URI parsing and transaction proof verificationNo changes to production wallet, consensus, or network codeNo bug fix or behavior change in existing source files
This Monero update fixes a bug in how nodes ask each other for blockchain history. Previously, a node could get stuck or drop a peer when it already knew about some blocks from another connection, because it would not ask for the next batc…
P2P protocol synchronization logic changePotential denial-of-service via peer dropping or sync stallNo authentication or cryptographic boundary crossed
This commit fixes a bug in how the Monero wallet saves itself to disk. Previously, the wallet could accidentally overwrite or corrupt its own files when the user chose a path that overlapped with existing wallet files, such as saving to a …
File overwrite / corruption prevention in wallet save path handlingSymlink and hardlink alias detection via filesystem equivalent() checksRejection of overlapping source/destination wallet files
074909c ringct: fix use-after-free of thread results in rct verification (jpk68)
ACKs: Ap4sh, selsta
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationprivacy or spend-authorization protocolmerge-commit duplicate discount
AI analysis · Moderate 63/100
This patch fixes a use-after-free bug in Monero's ring signature verification code. The bug occurred because a local results container was declared after the thread pool waiter object. In C++, local objects are destroyed in reverse order of creation, so the waiter (which waits for worker threads to finish) was being destroyed before the results container. If a worker thread still accessed the results container after the waiter was gone, it could read or write freed memory. The fix simply moves the results container to be declared before the waiter, ensuring it is destroyed after all threads are done with it. This is a memory-safety and potential correctness issue in transaction verification, but the patch is small and the practical exploit path is uncertain.
bcdd241 zmq: fix overflow in get_output_histogram recent_cutoff check (jpk68)
ACKs: Ap4sh, selsta
63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Moderate 50/100
This patch fixes a time comparison bug in Monero's restricted RPC daemon. The old code constructed a clock time point from a user-supplied number of seconds, which could overflow or produce a wildly wrong date. It then compared that date to 'now' to decide whether the requested histogram cutoff was too old. The new code converts 'now' to a plain second count, subtracts the allowed restricted window, and compares the resulting boundary directly against the user's value. This avoids constructing a time point from untrusted input and makes the age check more reliable. The practical security effect is likely limited because the call is only relevant on restricted RPC endpoints and the worst outcome appears to be an incorrect rejection or acceptance of a histogram request, not direct loss of funds or remote code execution.
da38ceb wallet2: require an output match before decrypting payment IDs (selsta)
ACKs: jpk68, UkoeHB
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolsigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 63/100
This change tightens when a Monero wallet tries to decrypt a short encrypted payment ID. Previously, the wallet would attempt decryption even when the transaction outputs were received via an additional (non-main) transaction public key. Now it only decrypts the payment ID when at least one output was received using the main transaction public key. This prevents a wallet from incorrectly associating a payment ID with a transaction that was not actually intended for the main address, which could lead to misattribution of payments or privacy issues.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 11/100
This commit only updates a submodule pointer for an external dependency called 'polyseed' from one commit hash to another. The actual code changes are not visible in this diff because submodules only store a reference to another repository's commit. There is no information in the commit message or diff indicating what changed inside polyseed or whether any of those changes relate to security.
11adb52 cryptonote_protocol: avoid pausing mining for known blocks (selsta)
ACKs: jpk68, SNeedlewoods
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 26/100
This small change adjusts when Monero pauses mining during block verification. Previously, mining was paused for every incoming block announcement, even for blocks the node already knew about. Now it only pauses for genuinely new blocks. The original code comment explicitly warned that pausing for every block might be a denial-of-service (DoS) risk, so this patch removes that potential abuse path. The practical effect is mainly a reduction in wasted mining time and a likely mitigation of a minor DoS vector, not a critical vulnerability fix.
4611f4f ryptonote_protocol: move full blob dumps to trace logs (selsta)
ACKs: SNeedlewoods, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 23/100
This change is a logging cleanup, not a fix for a code vulnerability. It moves full hex dumps of malformed network blobs from regular error logs to a special low-level 'trace' log category. The goal is to stop normal node logs from filling up with huge binary dumps when a peer sends bad data. The underlying behavior—rejecting malformed blocks and dropping the peer—stays exactly the same.
This commit fixes places where sensitive secret data (private key material and one-time derivation scalars) was left in memory after use instead of being securely erased. In three files, the patch adds explicit memory wipes or switches a temporary buffer to a locked, auto-scrubbing container. If an attacker could read the process's memory or capture a core dump, leftover secret values could leak. The patch is defensive and partial—it addresses additional cases beyond an earlier fix, suggesting the project is still finding spots that were missed.
This tiny change stops Monero nodes from cutting off network peers when a previously accepted transaction expires from the memory pool. Before the patch, an expired transaction could be treated as a peer offense and trigger a peer drop, which could be abused to isolate or partition nodes from the network. The fix marks the transaction validation result as 'no drop offense' so the peer connection is preserved.
511839d wallet: allow separate password for watch-only export (Samy)
ACKs: SNeedlewoods, jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 59/100
This Monero wallet patch changes how watch-only wallet exports are created. Previously, the exported watch-only file was encrypted with the same password as the original full wallet. Now users can set a separate password for the watch-only export. More importantly, the patch also strips sensitive material out of that export: it removes the Monero-C passphrase and disables/removes custom background-sync keys from the watch-only file. The code also verifies the original wallet password before creating the export. The change appears to be a security hardening fix for information leakage when exporting a watch-only wallet.
3f444f4 tests: tests_common library and gen_corpus executable (jeffro256)
ACKs: selsta, thomasbuilds, jpk68
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 19/100
This commit is a test-infrastructure change for the Monero cryptocurrency project. It adds a new helper library and a tool that generates fake transaction data for fuzz testing, plus a small constant defining the maximum hard-fork version supported by the code. It does not change how normal users' funds are handled, does not fix a live bug, and does not introduce an obvious way for an attacker to steal coins or crash running nodes. The main security-relevant aspect is that it improves automated testing of transaction parsing and validation, which can help find bugs in the future.
Security candidatep2p: restore safe DB sync after public peer disconnectsby Samy · 36b87ef8 · Oct 19, 2026 · 2 filesMessage 50 · ThinModerate 51Details
Commit message · Samy
p2p: restore safe DB sync after public peer disconnects
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathparser or protocol path
AI analysis · Moderate 51/100
This patch fixes how Monero nodes decide when to use a slower, safer database sync mode after losing a peer. Previously, a node could leave safe-sync off when only hidden-network peers (Tor/I2P) remained, or could turn it on incorrectly. The change now tracks public-internet peers separately and restores safe sync when a public peer disconnects, helping prevent database corruption if the remaining peers are on anonymous networks.
This commit adds a new X25519 cryptography wrapper and some build-system plumbing so the new code compiles correctly. It is a feature addition, not a fix for an active security hole. The new functions are not yet wired into any live protocol or wallet code in this commit, so they do not by themselves create an exploitable vulnerability. The change does include one notable design choice: the scalar-multiplication helpers are explicitly documented as "unclamped" and therefore do not follow the RFC 7748 standard, which could be risky if a future caller assumes standard behavior. The code also uses reinterpret_cast between Monero and an external mx25519 library types, relying on compile-time size/layout checks for safety.
d4ff199 cryptonote_protocol: validate borrowed spans against peer history (selsta)
ACKs: jpk68, plowsof
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Moderate 61/100
This Monero update tightens how a node checks block-download requests it has 'borrowed' from another peer. Before serving a borrowed range of blocks, the node now verifies that range against the peer's own known history. If the history is missing or doesn't match, the node either refreshes its chain knowledge or puts the peer on standby instead of blindly trusting the borrowed blocks. This reduces the chance that a malicious or inconsistent peer can feed a node the wrong chain during sync.
This is a routine version-bump and checkpoint update for the Monero cryptocurrency software. It updates the recommended software version from v0.18.5.3 to v0.18.5.4, refreshes the built-in list of trusted blockchain checkpoints to a newer block height, and updates the corresponding hash that verifies those checkpoints. These changes are part of normal maintenance and do not, by themselves, fix a known security vulnerability.
Security candidatesrc: update checkpoints to match v0.18.5.4by selsta · a8f92ca7 · Oct 14, 2026 · 4 filesMessage 45 · ThinInformational 21Details
Commit message · selsta
src: update checkpoints to match v0.18.5.4
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 21/100
This commit updates Monero's built-in blockchain checkpoints to match the latest release version (v0.18.5.4). Checkpoints are hard-coded reference points that help nodes quickly verify they are following the correct chain. The change does not appear to fix a security vulnerability; it is a routine maintenance update that refreshes the latest trusted checkpoint and the expected hash of the checkpoint file. The README is also updated to reference the new version number in build instructions.
bf03cb5 cryptonote_basic, epee: remove outdated todos (jpk68)
ACKs: selsta, PyXMR2025
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit only removes stale 'TODO' comments from four source files. No code behavior is changed, no bugs are fixed, and no security issue is introduced or addressed.
d3fb59f common: replace dnssec_valid bool with dnssec_status enum in openalias (Jackie)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 34/100
This change improves how Monero handles OpenAlias address lookups via DNS. Previously, the software only knew whether DNSSEC validation passed or not, treating 'not available' and 'invalid' the same. Now it distinguishes three states: DNSSEC unavailable, valid, or invalid. This lets the wallet and RPC give clearer warnings and reject addresses when DNSSEC actually fails validation, rather than silently treating unsigned domains the same as tampered ones. It is a defensive hardening change, not a fix for an active exploit.
0de7298 portable_binary_iarchive: check signature length before allocating (woodser)
ACKs: jpk68, selsta
63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarymerge-commit duplicate discount
AI analysis · Moderate 60/100
This patch fixes a way that a malformed file could trick Monero's Boost-based archive reader into trying to allocate a huge amount of memory. Before the fix, the reader would trust the length value encoded in the input and resize a string to that size, which could exhaust memory or crash the program. Now it first checks that the claimed length matches the expected archive signature length before allocating.
947167d ringct: revert range proof proving enum vals (jeffro256)
ACKs: plowsof, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
consensus or confidential-proof validationprivacy or spend-authorization protocolmerge-commit duplicate discount
AI analysis · Low 43/100
This tiny change reassigns numeric values to two internal labels used for Monero's range proof types. Instead of the labels automatically getting consecutive numbers (0, 1), they are now explicitly set to 0 and 3. The commit message says it 'reverts' an earlier change that had assigned them consecutive values. This is likely a backward-compatibility or serialization fix, because stored data or network messages may already expect the value 3 for the newer bulletproof range proof. On its own the patch does not look like an active exploit, but a mismatch in these numeric values could in theory cause two versions of the software to disagree about transaction data, which can be a security concern in a cryptocurrency.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This is a one-line code change that adds an explicit copy-assignment operator to a small helper class for the Polyseed mnemonic system. It only silences a compiler warning and does not change program behavior or fix any security issue.
5bd76fd blockchain_import: use pool supplements for block verification (selsta)
ACKs: thomasbuilds, jpk68
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 32/100
This Monero code change refactors how the blockchain import tool verifies blocks. Previously, the tool fed each transaction individually into the core for verification before processing the block. Now it builds a 'pool supplement' from the block's transactions and passes that directly to the block verifier, matching how the network protocol already handles blocks. The change also moves shared helper code into a common header and adds a duplicate-transaction check that was missing before.
This Monero update fixes a bug in how the transaction pool (mempool) handles transactions whose recorded arrival time is in the future. Before the fix, a transaction with a future receive_time could be treated as extremely old and wrongly removed from the pool, or cause misleading statistics. The patch clamps such times to the current time so they are not penalized. A new test confirms future-timestamped transactions stay in the pool while genuinely expired ones are still cleaned up.
This change is a performance optimization for the Monero transaction pool. It caches a 'prunable hash' when a transaction first enters the pool, so that later RPC lookups can reuse the cached value instead of recalculating it every time. There is no direct security vulnerability in the patch; it is intended to make the node faster and the RPC behavior more consistent. The commit message and diff do not describe any security bug or exploit.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 40/100
This change moves and tightens a limit on how many blocks a Monero node can request at once when syncing. Previously the limit was checked against a larger value (2048) and only logged an error without stopping startup. Now the same limit (100) is enforced earlier and more strictly, returning failure if exceeded. This prevents a node operator from configuring an oversized block-sync request that could strain memory or network handling.