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
This change adds a password check inside the wallet's key-encryption routine so that the wallet refuses to encrypt keys if the caller supplies the wrong password. Before, supplying an incorrect password could still trigger encryption, potentially leaving the wallet file in a state where the stored keys do not match the password the user actually knows. The patch is small and includes a new test that confirms the wrong-password case now throws an error.
AI review queuedMerge pull request #11546by tobtoht · 42dff4e5 · Oct 24, 2026 · 1 fileMessage 68 · AdequateModerate 57Details
Commit message · tobtoht
Merge pull request #11546
1388f36 wallet: verify password before make/exchange multisig (SNeedlewoods)
ACKs: jpk68, selsta
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This change adds a password check at the start of two wallet operations that create or modify multisignature ('multisig') wallets. Before the fix, these functions would proceed to decrypt the wallet's private keys using whatever password was supplied, even if it was wrong. With the fix, the password is verified first, so an incorrect password stops the operation before any sensitive key material is touched. This reduces the risk that an attacker with brief access to an unlocked wallet, or who supplies a wrong password, could trigger multisig operations or cause key-handling errors.
AI review queuedMerge pull request #11545by tobtoht · 539c5056 · Oct 24, 2026 · 2 filesMessage 58 · ThinModerate 59Details
✓ 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 59/100
This change fixes a bug in how Monero wallets import 'outputs' (records of received funds). Previously, if an import failed part-way through—because the wallet lacked a needed subaddress—the code could leave behind partially-created records. These incomplete records could later be mistaken for valid, spendable money, potentially causing the wallet to build transactions that fail or behave incorrectly. The patch now only adds fully validated records and cleans up properly if the total number shrinks. A new test confirms that a failed import does not leave incomplete transfers behind.
✓ 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 44/100
This change fixes how a Monero cold wallet handles imported output files that are empty or in an older format. Previously, the wallet could misread an empty export and either fail to clear stale outputs or incorrectly treat the old format as valid, which could lead to a cold wallet showing wrong balances or accepting incomplete state. The patch makes the logic clearer: try the new format first, and only if that fails try the old format. New tests confirm that after a blockchain reorganization an empty export correctly clears outputs, and that an empty incremental export cannot be used to rebuild a cold wallet from scratch.
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.
AI review queuedMerge pull request #11505by tobtoht · 0eb5a4d2 · Oct 24, 2026 · 2 filesMessage 58 · ThinInformational 19Details
Commit message · tobtoht
Merge pull request #11505
f3ebca3 wallet2: save address files for in-memory non-mainnet wallets (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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This change fixes a small inconsistency in how Monero wallets are saved. When a wallet was created only in memory and then saved to disk on a test or staging network, it was missing the plain-text '.address.txt' file that normally gets created alongside mainnet wallets. The patch makes sure that address file is also written for non-mainnet wallets. It is a bug-fix for file output consistency, not a vulnerability that lets an attacker steal funds or keys.
AI review queuedMerge pull request #11451by tobtoht · 1795c1c6 · Oct 24, 2026 · 2 filesMessage 58 · ThinModerate 65Details
Commit message · tobtoht
Merge pull request #11451
262d2b7 wallet2: harden ring size and output distribution checks (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
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 65/100
This Monero wallet patch fixes two related issues. First, it prevents the wallet from ever estimating a ring size of zero, which could have caused fee or transaction-building errors. Second, it tightens a check that validates the number of available spendable outputs reported by a remote daemon, making it harder for a malicious or buggy daemon to trick the wallet with a suspicious output distribution. The changes are defensive hardening rather than a clear remote exploit 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.
AI review queuedMerge pull request #11500by tobtoht · 5b5a6f50 · Oct 24, 2026 · 2 filesMessage 66 · AdequateInformational 18Details
Commit message · tobtoht
Merge pull request #11500
d9f462a simplewallet: calculate balance from account history in filtered exports (Samy)
ACKs: amin404ala*, jpk68, selsta
66/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ 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 18/100
This change fixes a bookkeeping quirk in Monero's command-line wallet export. Previously, when you filtered your transfer history (for example, showing only a date range or specific addresses), the running balance column was calculated only from the visible rows, so it could look wrong or misleading. Now the wallet secretly includes all confirmed transfers in the account when computing the running balance, while still only exporting the rows that match your filter. This is a user-experience/data-integrity fix, not a vulnerability that lets someone steal funds or break the blockchain.
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.
AI review queuedMerge pull request #11208by tobtoht · 9b580ca7 · Oct 24, 2026 · 25 filesMessage 66 · AdequateInformational 20Details
This commit swaps Monero's command-line input library from the external GNU readline to a vendored copy of linenoise. It is primarily a build-system and dependency-maintenance change. The new library is included directly in the repository, so Monero no longer relies on the system's readline/ncurses packages. There is no direct evidence in the commit message or diff that this fixes a specific security vulnerability; it looks like a routine dependency replacement.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
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.
711d442 epee: rearm idle handlers after exceptions (Samy)
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 #11447by tobtoht · 92886478 · Oct 17, 2026 · 2 filesMessage 58 · ThinInformational 19Details
Commit message · tobtoht
Merge pull request #11447
a3860e7 fix: wallet_info for non-deterministic wallets (SNeedlewoods)
ACKs: PyXMR2025*, 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 · Informational 19/100
This change only improves how wallet software reports what kind of wallet and seed type the user has. It adds labels for hardware wallets and non-deterministic wallets, and fixes cases where a watch-only or hardware wallet was previously mislabeled. There is no security vulnerability here—just better, more accurate user-facing text.