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
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedMerge pull request #11603by tobtoht · 7b3f6271 · Nov 16, 2026 · 1 fileMessage 58 · ThinModerate 57Details
Commit message · tobtoht
Merge pull request #11603
6874328 wallet2: keep inputs spent by a confirmed tx when a pending tx fails (woodser)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 57/100
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 try to spend the same coins again, leading to failed transactions, confusion, or in the worst case creation of a double-spend attempt that the network would reject. The fix tells the wallet to leave the 'spent' flag alone when a failure occurs if the coins were already spent by a confirmed transaction.
AI review queuedMerge pull request #11492by tobtoht · 4014125f · Nov 16, 2026 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · tobtoht
Merge pull request #11492
d9fde36 OSS-Fuzz: Add new fuzzer targets wallet proof process (Arthur SC Chan)
ACKs: PyXMR2025, jpk68, 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
fuzzing or regression evidencesigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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, not a security patch for an existing issue.
08fa170 cryptonote_protocol: ask for the next chain entry when the last one is known (0xfffc0000)
ACKs: Ap4sh*, selsta, jpk68, thomasbuilds
66/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 27/100
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 batch of hashes. The patch lets a node recognize when it already has enough of a peer's promised chain and request the following chunk instead. It is a network-synchronization robustness improvement rather than a direct theft or remote-code-execution vulnerability.
bb84dc0 p2p: restore both anchor connections after a restart (0xfffc0000)
ACKs: thomasbuilds, jpk68, SNeedlewoods, selsta
66/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedwallet2: handle .keys saves and overlapping pathsby Samy · 4cc0e506 · Nov 15, 2026 · 2 filesMessage 45 · ThinModerate 65Details
Commit message · Samy
wallet2: handle .keys saves and overlapping paths
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 65/100
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 whose name ends in '.keys' or using symbolic links. The patch makes the wallet detect these overlapping paths and refuse unsafe saves, while still allowing normal saves. It also adds many automated tests to confirm the behavior.
Lower-priorityfcmp_pp: link Windows synchronization after Rustby Samy · 43b7aa04 · Nov 14, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Samy
fcmp_pp: link Windows synchronization after Rust
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedMerge pull request #11691by tobtoht · ef78ff3d · Nov 13, 2026 · 2 filesMessage 58 · ThinModerate 50Details
Commit message · tobtoht
Merge pull request #11691
a56d2d9 simplewallet: omit command arguments from debug logs (Samy)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 50/100
This change stops Monero's command-line wallet from writing full command arguments, including passwords or other secrets, to its debug log files. Previously, when a user typed a command with arguments, the entire line could be recorded in logs at the debug level. Now, only the command name is logged, while arguments are stripped out. This reduces the risk that sensitive information accidentally ends up in log files where it could be read later by another user or process.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedMerge pull request #11686by tobtoht · 73b083c5 · Nov 13, 2026 · 4 filesMessage 58 · ThinModerate 60Details
Commit message · tobtoht
Merge pull request #11686
090d6d8 simplewallet: keep multisig info and tx keys out of logs (Samy)
ACKs: selsta, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This update changes the Monero wallet so that two especially sensitive pieces of information—multisig setup data and transaction secret keys—are still shown to the user on screen but are no longer written to the wallet's log files. Before, the same on-screen message routine also saved those messages to disk, which could leave private key material in persistent logs. The patch adds an 'unlogged' message writer and uses it for these two cases, plus adds a test to confirm the behavior.
3c9209d rpc: refuse to overwrite existing update destinations (selsta)
ACKs: jpk68, vtnerd
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedMerge pull request #11679by tobtoht · 1785a958 · Nov 13, 2026 · 4 filesMessage 58 · ThinInformational 19Details
Commit message · tobtoht
Merge pull request #11679
79ddfda wallet_api: expose double-spend for incoming pool payments (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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This change adds a new read-only flag to Monero wallet transaction records that tells users whether an incoming unconfirmed payment has been seen in a suspected double-spend attempt. It does not change how transactions are validated or accepted by the network; it only exposes information that was already tracked internally so wallet interfaces can display a warning. There is no direct security fix here, but it helps wallet users avoid trusting a payment that might later disappear from the blockchain.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 60/100
This update fixes a flaw in Monero's wallet message-signing feature. Previously, a wallet that only held a view key (a 'view-only' wallet) could be asked to sign a message as if it held the spend key, producing a signature that looked valid but was actually created with the wrong private key. The fix makes the wallet verify it actually possesses the requested signing key before creating any signature, and it also adds checks that the requested address truly belongs to the wallet. This prevents misleading or unverifiable signatures from being generated.
AI review queuedMerge pull request #11666by tobtoht · e69ad3af · Nov 13, 2026 · 1 fileMessage 58 · ThinInformational 19Details
Commit message · tobtoht
Merge pull request #11666
21ee5af wallet_args: remove stale macos max-concurrency default (jpk68)
ACKs: selsta, thomasbuilds
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This change removes an old Apple-only workaround that forced Monero wallet software to use just one thread by default. On macOS, the wallet will now use the same default (0, meaning automatic) as other operating systems. This is a cleanup of stale code, not a fix for an active security vulnerability.
AI review queuedMerge pull request #11619by tobtoht · f622545e · Nov 13, 2026 · 7 filesMessage 66 · AdequateModerate 63Details
Commit message · tobtoht
Merge pull request #11619
f01cee3 simplewallet: handle signals in a separate thread (jpk68) 35b2b6e simplewallet: print all seeds directly to stdout (jpk68) 0216b74 epee: lock, drain and wipe console output (jpk68) 22bd3f0 linenoise: harden input, support dumb terminals (jpk68)
ACKs: selsta, thomasbuilds
66/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 63/100
This Monero update hardens the command-line wallet's console handling. It prevents wallet recovery seeds and secret keys from sitting in standard output buffers, makes signal handling (like Ctrl-C) safer so the wallet doesn't crash or misbehave, and improves how long input lines and unusual terminals are handled. These are defensive fixes that reduce the chances of sensitive data leaking through logs, terminal history, or memory, and make the wallet more stable when interrupted.
This commit adds the verification side of a new Monero privacy feature called FCMP++ (Full Chain Membership Proofs). It is not a fix for a known bug or vulnerability; it is new code that lets the network check FCMP++ proofs in transactions. The change also updates a Rust dependency and adds tests and performance tooling. There is no evidence in the commit message or diff that this is a security patch or that it addresses any disclosed vulnerability.
AI review queuedMerge pull request #11662by tobtoht · 046e926d · Nov 9, 2026 · 2 filesMessage 58 · ThinLow 43Details
Commit message · tobtoht
Merge pull request #11662
7672a71 wallet2: handle unlocked keys-file status (Samy)
ACKs: selsta, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 43/100
This patch fixes a crash in the Monero wallet software. The wallet could try to check whether a sensitive 'keys file' was locked even when no such file existed, causing the program to dereference a null pointer and crash. The fix adds a simple safety check before using the file-lock object. The crash is not a remote exploit, but it could make the wallet unavailable or, in some edge cases, lead to undefined behavior.
AI review queuedMerge pull request #11660by tobtoht · a5257294 · Nov 9, 2026 · 2 filesMessage 58 · ThinInformational 19Details
Commit message · tobtoht
Merge pull request #11660
01dfcd6 wallet_rpc_server: reopen log file on `SIGUSR1` (Samy)
ACKs: selsta, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This change lets the Monero wallet RPC program reopen its log file when it receives a special Unix signal (SIGUSR1). This is a convenience feature for log rotation, matching behavior already present in the main Monero daemon. It is not a security fix and does not appear to introduce a meaningful vulnerability.
AI review queuedMerge pull request #11618by tobtoht · 7ec1ae21 · Nov 9, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · tobtoht
Merge pull request #11618
162436a simplewallet, epee: accept 'quit' to exit the console (jpk68)
ACKs: selsta, thomasbuilds
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds 'quit' as an additional keyword to exit the Monero command-line wallet and console handler, alongside existing 'exit' and 'q' commands. It is a minor user-experience improvement with no security relevance.
83fdff2 cryptonote: support pruned weights for old RingCT (Samy)
ACKs: jpk68, selsta
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 protocolcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 35/100
This Monero update extends the software's ability to estimate the size (weight) of older, pruned RingCT transactions. Previously, the code only handled newer Bulletproof-style transactions, which could cause nodes running with pruned blockchains to refuse or mishandle older blocks. The change also lets pruned syncing start earlier in Monero's history. It is a correctness/robustness fix rather than a direct theft or remote-code-execution bug.
This commit adds native I2P SAM (Simple Anonymous Messaging) protocol support to Monero, allowing the daemon to connect directly to I2P routers instead of requiring a separate SOCKS proxy. It introduces new network code, command-line options, and changes to how incoming and outgoing peer connections are established. The change is a feature addition rather than a documented security fix, but it touches low-level networking and anonymity code, so implementation flaws could affect privacy or stability.