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 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 are not spendable too early, and simplifies how transparent (non-hidden) coin amounts are collected. There is no direct evidence in the commit that this fixes an active exploit; it reads as hardening and code-quality improvements following a larger earlier change.
Security candidatedb: cleanup following PR #11425by koe · e108199d · Nov 18, 2026 · 8 filesMessage 53 · ThinLow 25Details
Commit message · koe
db: cleanup following PR #11425
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 25/100
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, rewrites a helper function to avoid an unnecessary indirection, and improves comments. There is no direct evidence in the commit that an exploitable vulnerability exists; rather, the changes reduce the chance of future bugs in how Monero tracks spendable outputs for its new FCMP++ membership proofs.
fc1e7c5 src: use compiler-defined win32 macro (jpk68)
ACKs: selsta, tobtoht
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 · Informational 19/100
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 reliable and portable. There is no direct security vulnerability being fixed here, though using the compiler-defined macro reduces the risk of build misconfiguration on Windows.
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 denial-of-service hardening change, not a fix for a currently exploitable vulnerability. The commit message and code comments describe it as a caching improvement, not a security patch.
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 re-enter the same database locks held by the caller. The fix fetches only the raw, pruned transaction blobs directly from the database and parses just the transaction base, avoiding the broader locking path. A functional test was added to verify the coinbase sum matches the block reward and reported fee.
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.
✓ 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.
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.
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.
This change adjusts how a specific warning/check (Undefined Behavior Sanitizer's 'shift-base' check) is handled for one cryptographic source file. It disables that sanitizer check when compiling crypto-ops.c, because that file intentionally left-shifts negative numbers as part of its math. It also removes a duplicate copy of the file from the test build. This is a build-system hygiene fix, not a patch for an exploitable vulnerability in the running code.
This change fixes a privacy leak in the Monero daemon. When a user ran the node through a proxy and had disabled DNS leaks, the daemon's manual 'update' RPC commands could still perform DNS lookups to check for new software versions. The patch now blocks those update checks when DNS is disallowed, preventing the user's real IP from being exposed via DNS queries.
This commit adds a new command-line option, --rpc-restricted-no-login, that lets a Monero node operator run a separate restricted RPC port without requiring HTTP digest authentication. It is an intentional feature, not a hidden backdoor, and the code enforces that the option can only be used together with the separate restricted RPC port. The change is defensive in design: it does not remove authentication from the main RPC port and explicitly prevents accidental misconfiguration.
This patch fixes a bookkeeping bug in Monero's transaction memory pool. When a new transaction was added, the code sometimes failed to mark it as a 'double spend' even when another part of the system had already detected a conflict. The fix makes the pool record the double-spend warning from the validation step, not just from a later secondary check. A missing flag could let conflicting transactions sit in the pool longer than they should, potentially affecting which transactions miners see or how nodes relay them.
a1e2501 src, epee: remove more unneeded comments (jpk68)
ACKs: selsta*, SyntheticBird45*, tobtoht
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 · Informational 15/100
This commit only removes blank comment lines and an old TODO note from source code. No program logic, security checks, or behavior was changed. It is a cleanup change with no security relevance.
d67e1cb cryptonote_protocol: skip hidden peers on stripe (Thomas)
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 pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 37/100
This small Monero patch changes how a node selects peers when syncing pruned blockchain data. It now skips over hidden/non-public peers (such as Tor/i2p connections) during a step that divides sync work among peers by 'stripe.' The goal appears to be to avoid giving sensitive sync coordination roles to anonymous peers, which could more easily be used to disrupt or spy on a node's sync process. The change is defensive and reduces attack surface, but the commit message does not frame it as a security fix.
675e2f0 wallet2: reject cold signing and output imports for multisig (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
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 59/100
This update blocks three wallet operations for Monero multisignature (multisig) wallets: ordinary cold signing of transactions, loading/parsing ordinary signed transactions, and importing output lists. Previously these operations may have been reachable for multisig wallets, which could bypass the special multisig signing workflow and potentially produce invalid or unsafe transactions. The fix adds explicit checks that throw errors or return false when a multisig wallet tries to use the non-multisig paths.
a6db2ef wallet2: import empty v2 outputs when signing (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 boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 59/100
This Monero wallet patch fixes a bug in cold-wallet signing where the full (offline) wallet could incorrectly trim or fail to update its list of spendable outputs when the watch-only wallet sent it an empty output export. The fix makes the offline signer recognize a special 'empty trim' signal in newer transaction export files, so it can safely discard outputs that the watch-only wallet no longer sees—such as after a blockchain reorganization—without losing other valid outputs. If left unfixed, a signer might try to spend outputs that no longer exist, or fail to sign valid transactions, but it does not appear to let an attacker steal funds directly.
This Monero commit refactors how the transaction pool (mempool) picks transactions for miners to put in the next block. It replaces an older method with a new 'block template backlog' system that can deliberately return slightly more transactions than a block can hold (called 'overpick'), so the miner has a buffer to work with. The change also switches the in-memory key-image-to-transaction map from a one-way map to a two-way map (boost::bimap), which is intended to make it easier and safer to remove transactions and detect double spends. The commit is described by its author as an improvement to backlog handling, not as a security fix, and no independent security advisory or CVE is supplied.
36b87ef p2p: restore safe DB sync after public peer disconnects (Samy)
ACKs: selsta, thomasbuilds, 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 · Moderate 51/100
This patch changes how Monero nodes decide when to switch back to a slower, safer database synchronization mode after a peer disconnects. Previously, the node could leave fast sync mode based on the highest reported blockchain height from any remaining peer, including peers on anonymous networks like Tor or I2P. Now, the node only uses publicly reachable peers to decide whether to re-enable safe sync. This reduces the chance that a single anonymous peer can trick a node into staying in fast sync, which could theoretically make certain denial-of-service or chain-manipulation attacks easier.
✓ 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 59/100
This Monero update tightens how a node checks another node's claims about being fully synced. Previously, a peer could trick a node into thinking it was synchronized by simply claiming a high block height. The patch now verifies that the peer's claimed top block actually matches the local node's known blockchain tip, and rejects absurdly large height values. This reduces the risk of a malicious or buggy peer prematurely ending a node's initial sync, which could leave the node on a stale or forked view of the network.
This is a large feature merge for Monero that adds database support for FCMP++ (Full Chain Membership Proof++) curve trees. It changes how outputs are indexed, adds new database tables, and includes a migration from database version 5 to 7. The changes are primarily structural and preparatory for a future privacy upgrade, not a finished activated protocol change. The code is gated behind a compile-time flag ENABLE_FCMP_INTEGRATION that is off by default.
561e6a8 wallet2: accept omitted key images when already synchronized (selsta)
ACKs: jpk68, jeffro256, 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 · Low 32/100
This change lets a Monero wallet accept signed transaction files even when the file does not include the usual list of key images, as long as the wallet already knows those key images itself. It is a usability fix for stateless or offline signers, not a clear security bug fix. The patch adds checks to make sure the wallet really does know the key images before it proceeds, so it appears defensive rather than dangerous.
a52a889 cryptonote_protocol: validate known top height (Samy)
ACKs: jpk68, selsta, thomasbuilds
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 a peer's claim about its copy of the blockchain. Before, a node would trust a peer if it simply recognized the peer's 'top block' hash, even if the peer lied about the block height. Now, for public internet peers, the node verifies that the claimed height actually matches the known block. If the height is wrong, the peer is penalized and disconnected. This prevents a type of network-level misinformation where a malicious or buggy peer could make others believe the chain is taller or shorter than it really is.
This patch fixes how Monero's blockchain code builds empty 'block templates' when a miner or pool explicitly asks for a template based on the current chain tip. Before the fix, the code used a rough estimate of block weight instead of the accurate current median, which could produce templates that don't match the real main-chain rules. The mismatch could let a miner create a block that other nodes reject, or cause inconsistent rewards/fees between normal and explicit tip templates. A new test confirms that explicit-tip templates now behave identically to normal ones.