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
Nice early check on allowed n key offsets per tx based on the guaranteed ceiling for the entire chain.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 59/100
This commit adds an early safety check to Monero's transaction parsing code. It rejects transactions that contain an impossibly large number of 'key offsets'—the references that identify which previous transaction outputs a transaction is spending from. The limit is based on the maximum allowed transaction size, so any transaction exceeding it cannot be valid anyway. The change is defensive and prevents malformed or oversized transaction data from being processed further.
AI review queueddevice_ledger: fix some commentsby jpk68 · e38cfe66 · Aug 7, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · jpk68
device_ledger: fix some comments
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only fixes spelling and wording in code comments (for example, changing 'Minimal' to 'Minimum' and 'lock' to 'unlock' where the comment was describing the wrong function). No actual program logic, function behavior, or security mechanism was changed.
Security candidatetx_pool: fix write abort and improve locking for relayable txsby jeffro256 · 77acf1f9 · Aug 7, 2026 · 1 fileMessage 50 · ThinLow 41Details
Commit message · jeffro256
tx_pool: fix write abort and improve locking for relayable txs
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 41/100
This patch tightens up how Monero's transaction pool records when to next re-broadcast relayable transactions. Previously, a database transaction was held open while iterating over all candidate transactions; now the lock is taken only when there are actual timestamp updates to write, and each update is wrapped in its own try/catch so one failing update does not abort the whole batch. The commit title says it fixes a 'write abort' and improves locking. The change reduces the chance that a transient database error or a single bad metadata update rolls back every scheduled relay update, which could have caused transactions to be re-relayed too soon or too late and potentially leak timing information about Dandelion++ routing.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritytests: update gtest to 1.17.0by Samy · 7fde08f0 · Aug 6, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Samy
tests: update gtest to 1.17.0
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritydevice: report ledger state when no app is openby reservedbytes · 2648a4a3 · Aug 6, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · reservedbytes
device: report ledger state when no app is open
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatep2p: update peer's height on new block & widen window for relayby j-berman · a47a4365 · Aug 6, 2026 · 2 filesMessage 85 · StrongLow 38Details
Commit message · j-berman
p2p: update peer's height on new block & widen window for relay
- We select peers to relay to based on their latest known sync height. - This change: A) makes sure to update the peer's latest known sync height upon validating the peer's newly relayed blocks. B) Allows for a wider window so that if we haven't yet received the peer's block or finished validating it, then the peer can still be a valid candidate to receive our new txs.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
cryptography-sensitive pathparser or protocol path
AI analysis · Low 38/100
This Monero patch fixes how the node keeps track of other peers' blockchain heights and who gets to receive new transactions. Previously, a node might think a peer was behind and stop sending it transactions, even when the peer actually had the latest block. The patch updates the peer's height when a new block is validated and allows a small two-block tolerance when choosing transaction-relay peers. The main risk if this were buggy or absent is degraded network propagation: transactions or blocks might spread more slowly, which can hurt network health and potentially be exploited to gain timing advantages (for example, in mining or double-spend scenarios).
Display the first non-zero change address after verifying that all effective change uses the same address. Foreign change is already rejected during signing, so this only fixes misleading display.
Reported by xmrack and the MAGIC Monero Fund.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 24/100
This commit fixes a display-only bug in Monero wallets. When a transaction is split into multiple parts, the wallet was showing the change address from the first transaction piece, even if that piece had no change. The fix makes it show the first piece that actually has change. The commit message says misleading display is the only effect because foreign change addresses are already rejected during signing, so no money could be sent to an attacker's address.
AI review queuedsrc: remove unused headersby jpk68 · cb88c71e · Aug 6, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · jpk68
src: remove unused headers
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply removes header files that were included in source code but not actually needed. It is a routine cleanup with no functional change to the Monero software and no security relevance.
Security candidatesrc: fix issues found through static analysisby jpk68 · fccaccbc · Aug 6, 2026 · 7 filesMessage 45 · ThinLow 26Details
Commit message · jpk68
src: fix issues found through static analysis
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathparser or protocol path
AI analysis · Low 26/100
This commit fixes several issues flagged by static analysis tools. Most changes add missing virtual destructors to C++ interface/base classes and remove unused function declarations. Missing virtual destructors can cause subtle memory bugs when objects are deleted through a base-class pointer, but the commit does not show any active crash or exploit path. It is a cleanup/hardening patch rather than a fix for a known active vulnerability.
AI review queuedwallet2: honor max_blocks bound during fast_refresh hash pullsby woodser · 669f90eb · Aug 6, 2026 · 2 filesMessage 50 · ThinLow 26Details
Commit message · woodser
wallet2: honor max_blocks bound during fast_refresh hash pulls
50/100 · ThinMessage clarity
✓ Specific, 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 · Low 26/100
This change adjusts how a Monero wallet fetches block hashes during its fast refresh mode. Previously, fast_refresh could keep pulling hashes without respecting the caller's max_blocks limit, which could make a single refresh call run for a very long time and appear unresponsive. The patch caps the number of hash pulls per refresh call and lets the wallet resume later, improving responsiveness. It is a robustness/usability fix rather than a clear-cut security vulnerability, though unbounded network loops can sometimes be abused to delay or hang wallet operations.
AI review queuedChange p2p connection map from raw pointers to weak_ptrsby Lee Clagett · b8028e31 · Aug 5, 2026 · 11 filesMessage 50 · ThinModerate 61Details
Commit message · Lee Clagett
Change p2p connection map from raw pointers to weak_ptrs
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Moderate 61/100
This commit refactors how Monero's peer-to-peer networking layer tracks active connections. Previously, the code stored raw pointers to connection objects in a central map and used manual reference counting (add_ref/release) to try to prevent those objects from being destroyed while still in use. The patch replaces that with std::weak_ptr and std::shared_ptr, so the map only holds non-owning weak references and the connection objects are kept alive automatically by shared_ptr ownership. This is a defensive hardening change that reduces the risk of use-after-free, double-free, and race-condition crashes in network handling. It is not an obvious remote exploit by itself, but it fixes a class of memory-safety bugs that could be triggered by malicious or unstable peers.
Security candidatecryptonote_core: rm unnecessary db reads before block relayby j-berman · ce14fdc0 · Aug 4, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · j-berman
cryptonote_core: rm unnecessary db reads before block relay
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 26/100
This commit removes several database checks that Monero performed before forwarding a newly received block to other peers. Previously, the node verified that it had all the block's transactions and that no blockchain reorganisation had happened. Now it relays the block immediately with fewer checks. The stated goal is performance, but the change could allow invalid or stale blocks to be relayed more easily, potentially contributing to network confusion or denial-of-service. There is no direct evidence in the commit that this fixes a known security bug or that it introduces an exploitable vulnerability.
Security candidateblockchain: if block is known invalid, fail block verificationby j-berman · 20db2e71 · Aug 4, 2026 · 1 fileMessage 60 · AdequateModerate 58Details
Commit message · j-berman
blockchain: if block is known invalid, fail block verification
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Moderate 58/100
This change fixes a logic bug in Monero's blockchain handling. Previously, when the software saw a block it already knew about, it would simply mark it as 'already exists' and move on, even if that block had previously been flagged as invalid. After the patch, if a known-invalid block is seen again, the verification is now correctly marked as failed. This prevents an invalid block from being treated as harmless on re-submission and could stop certain denial-of-service or chain-integrity attacks.
AI review queueddevice_trezor: update protobuf definitionsby jpk68 · 576af29b · Aug 4, 2026 · 9 filesMessage 35 · OpaqueLow 27Details
Commit message · jpk68
device_trezor: update protobuf definitions
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 27/100
This commit updates Monero's Trezor hardware wallet integration to match newer Trezor firmware protobuf definitions. It adds support for new device features (brightness, language packs, authenticity proofs, debug tools, etc.), renames some message types, and moves protobuf extension options into a separate file. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a compatibility update to keep Monero working with current Trezor firmware.
AI review queuedwallet_rpc_server: add weight to describe_transferby Samy · 60493c3a · Aug 4, 2026 · 4 filesMessage 50 · ThinInformational 19Details
Commit message · Samy
wallet_rpc_server: add weight to describe_transfer
50/100 · ThinMessage clarity
✓ Specific, 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 · Informational 19/100
This commit adds a new 'weight' field to the Monero wallet RPC command that describes a transaction. It is a routine feature enhancement: the server now reports how large (in bytes/weight units) a transaction is, which helps users estimate fees. There is no indication of a security bug being fixed.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedsimplewallet: tweak description of donate commandby jpk68 · 9bd5f7ee · Aug 4, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · jpk68
simplewallet: tweak description of donate command
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 · Informational 15/100
This commit only changes two user-facing text strings in the Monero command-line wallet. It rewords the description of the built-in 'donate' command from 'development team' to 'general fund'. There is no code behavior change, no security fix, and no vulnerability introduced.
wallet: display private view keys for hardware wallets
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
privacy or spend-authorization protocolsigning or wallet path
AI analysis · Informational 18/100
This change lets users of Ledger hardware wallets see their private view key in the Monero command-line wallet, something previously hidden with the message 'On device. Not available.' The key is already cached inside the wallet software for normal operation; the patch simply exposes it through the existing `viewkey` command when the user asks. It does not appear to leak the key to anyone else or bypass hardware protections for the spend key.
wallet2: validate key image domain in reserve proofs
Reported by zkao, a tool by zkSecurity
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationprivacy or spend-authorization protocolsigning or wallet path
AI analysis · Moderate 60/100
This change adds a safety check when a Monero wallet verifies a 'reserve proof'—a document that supposedly proves someone owns enough funds without revealing which coins they are. The fix rejects reserve proofs that contain a mathematically invalid 'key image' (the special value zero, or a point outside the allowed cryptographic subgroup). Without this check, a maliciously crafted proof might trick the wallet into accepting or behaving unexpectedly on data that violates the protocol's assumptions.
wallet_api: reject transaction file signing with hardware wallets
Reported by zkao, a tool by zkSecurity
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 46/100
This change blocks a specific command—signing unsigned transaction files—from being used when a Monero wallet's private keys live on a hardware device (Ledger/Trezor). Before the patch, the software apparently allowed users to attempt this operation, which hardware wallets do not actually support. The patch now returns a clear error instead of proceeding. The risk is that a user or third-party tool could be misled into thinking a transaction was properly signed when it was not, potentially causing loss of funds or a failed/confused workflow. No exploit code is shown in the commit.
rpc: hide sensitive txs from restricted block templates
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 63/100
This Monero patch changes how block templates are built for restricted RPC users. Before, a remote user calling the get_block_template RPC on a restricted node could receive a block template containing sensitive transactions—specifically transactions that were relayed privately (such as Dandelion++ stem transactions). The patch adds a flag so restricted RPC callers get a template that only includes publicly broadcast transactions, while local/unrestricted callers still get the full template. This reduces information leakage about pending private transactions to untrusted RPC clients.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queueddepends: native_protobuf: don't include debug symbols in protoc binaryby tobtoht · d4b681c1 · Aug 2, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · tobtoht
depends: native_protobuf: don't include debug symbols in protoc binary
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit changes how the Monero build system compiles the protocol buffer compiler (protoc), a developer-only tool used during the build process. It adds a compiler flag to strip debug symbols from the protoc binary. This is a build-hygiene change: it makes the resulting tool smaller and avoids shipping unnecessary debugging information. It does not fix a vulnerability in Monero's runtime code, nor does it change how Monero nodes or wallets behave. At most, it removes a minor information-leakage path (debug symbols could reveal build paths or function names) from a build-time tool, and slightly reduces attack surface by making the binary smaller and simpler.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 46/100
This commit fixes an off-by-one error in a wallet fee calculation. The original code allowed an index equal to the array size, which could read one element past the end of a fee lookup table. This could cause the wallet to use incorrect fee data or crash, but the commit message only describes it as a 'faulty bounds check' with no security framing.