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
simplewallet: rename duplicate amount headers for clarity
There are duplicate 'amount' headers when using export_transfers all. Column five represents the transaction total while column eleven represents the amount transferred per destination.
Rename the columns without changing their order or values.
(cherry picked from commit 30ab49d5cb5f7d5b089d20919cf4f02b063f2e6b)
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only renames two CSV column headers in the Monero wallet's export_transfers output from 'amount' to 'transaction amount' and 'destination amount' to make them less confusing. No numbers, logic, or behavior changed.
wallet_api: expose signed message verification details
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 validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit adds a new wallet API function that exposes more details when verifying a signed message, such as which key was used and which signature version was detected. It does not change existing behavior; the old simple true/false check still works exactly as before. There is no indication this fixes a security bug or introduces a vulnerability.
cryptonote_basic: cache prunable hash for pruned 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 · Informational 19/100
This commit adds a small internal optimization to Monero's transaction handling: when a transaction is pruned (stripped of some data to save space), the hash of the removed 'prunable' part is now saved inside the transaction object. This avoids having to recompute or re-supply that hash later. The change is accompanied by a unit test that verifies the cached hash matches the independently computed one. There is no direct security vulnerability visible in the diff; it appears to be a correctness/performance improvement for pruned transaction validation.
AI review queuedwallet2: exclude outputs from an unconfirmed send in reserve proofsby Cole Munz · ba3884e4 · Aug 31, 2026 · 1 fileMessage 81 · StrongModerate 60Details
Commit message · Cole Munz
wallet2: exclude outputs from an unconfirmed send in reserve proofs
get_reserve_proof picks outputs with is_spent(td, true). That only counts an output spent once its spending tx has confirmed. commit_tx marks an output spent as soon as the tx goes to the daemon, well before it confirms. spent_height stays 0 until then. So an output already used as input to a pending send still passes as unspent here.
A wallet can prove reserve over outputs it already committed to a pending send. check_reserve_proof reports them unspent, but they are gone as soon as that send confirms. Reported with a stagenet repro in #6595.
Switched to is_spent(td, false), which the wallet's default balance already uses for this reason. Both the zero-balance guard and the account_minreserve check used to go through balance_all()/balance(), which fold in change and self-transfer amounts from our own unconfirmed txs (m_unconfirmed_txs, m_unconfirmed_payments). Those amounts have no matching row in m_transfers yet, so once an output is tied up in a pending send, is_spent(td, false) drops it from selected_transfers while the pending change keeps the balance call non-zero, and the guard passes over an empty or thinner selection than it should. Now both guards sum selected_transfers directly, computed once, so they match exactly what the proof is built over.
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This fix corrects a Monero wallet bug where a user could generate a cryptographic 'reserve proof' claiming they still owned money that they had already committed to spending. Before the patch, the wallet only excluded outputs from the proof once the spending transaction was confirmed on the blockchain. Because the wallet marks outputs as spent earlier—when the transaction is first submitted to the network—a user could honestly but incorrectly prove reserve over outputs that would disappear as soon as the pending send confirmed. The patch makes the wallet treat pending-spent outputs as unavailable and checks the exact outputs selected for the proof rather than a broader balance figure that could include pending change.
Lower-priorityfish: fix tx-proxy completion spellingby Ming Code · 0e269757 · Aug 31, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Ming Code
fish: fix tx-proxy completion spelling
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedlmdb: correct environment error spellingby Ming Code · d8a43636 · Aug 31, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Ming Code
lmdb: correct environment error spelling
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 fixes a typo in two user-facing error messages, changing 'LDMB' to 'LMDB'. It does not change any program logic, database handling, or security behavior.
Lower-prioritytests: cover restricted add_aux_pow limitby Ming Code · 26355f01 · Aug 31, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Ming Code
tests: cover restricted add_aux_pow limit
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritydoc: declare draft-07 schema metadataby ming · c727e348 · Aug 30, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · ming
doc: declare draft-07 schema metadata
Keep the published ZMQ schema documents consistent by declaring the JSON Schema draft used by pub_chain_full.json.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 44/100
This commit fixes a crash or incorrect-behavior bug in Monero's Groestl hash function when given data that is not aligned to a 4-byte memory boundary. The old code read the input directly as 32-bit words, which can fail on some processors or compilers that require aligned memory access. The fix copies the bytes one word at a time using memcpy, which is safe for any memory address. A new unit test verifies that hashing the same bytes at different alignments produces the same result.
Security candidateAdd checks in cryptonote serialization routineby Lee *!* Clagett · 2fe75344 · Aug 30, 2026 · 4 filesMessage 45 · ThinModerate 65Details
Commit message · Lee *!* Clagett
Add checks in cryptonote serialization routine
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 65/100
This commit adds size and bounds checks to Monero's serialization code, which converts blockchain data between raw bytes and usable structures. The changes prevent the code from trying to read more data than is actually available, and stop attackers from tricking the node into reserving huge amounts of memory based on a maliciously crafted message. In short, it hardens the network parsing layer against malformed data that could crash nodes or exhaust resources.
✓ 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 18/100
This is a tiny user-interface wording change in Monero's command-line wallet. It changes when and how a 'suggested threshold' of confirmations is shown to the user when viewing a transfer. Previously, the threshold was shown whenever it was greater than zero. Now, it is only shown when the actual number of confirmations is still below that threshold. Once the threshold is reached, the extra text is hidden. This is a cosmetic change, not a security fix.
AI review queuedsimplewallet: quote notes in transfer exportsby Samy · e96e9e66 · Aug 29, 2026 · 1 fileMessage 45 · ThinLow 33Details
Commit message · Samy
simplewallet: quote notes in transfer exports
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 · Low 33/100
This change fixes a CSV export bug in Monero's command-line wallet. User-written notes attached to transfers were written into the export file without surrounding quotes, while other fields were quoted. If a note contained a comma, the exported CSV would have extra columns, and if it contained a quote, the file could become malformed. This is a data-integrity/formatting fix rather than a code-execution vulnerability, but it could mislead users or break import into spreadsheet software.
epee, common: pass unsigned char to <cctype> functions
The <cctype> functions require their argument to be representable as unsigned char or to equal EOF. char is signed on the platforms Monero targets, so every byte >= 0x80 reaches them negative, which is undefined behaviour.
All six call sites take bytes that come from outside the process:
hex_to_dec_2bytes() percent-escapes in a payment URI http_client.h the status line of an HTTP response updates.cpp the hash field of a DNS update record
glibc and the macOS libc happen to tolerate -128..-1 because their tables carry padding below zero, so this is quiet in practice on those, but it is still out of contract and other libcs index without that cushion.
Cast to unsigned char at each call. The conversion is behaviour-preserving for the ASCII these actually test: for a byte such as 0xC3, toupper() returns it unchanged in the C locale, it narrows back to char, memchr() misses it in the hex table, and hex_to_dec_2bytes() falls through to the existing literal "%XY" output exactly as before.
epee::misc_utils::parse::isdigit/isalpha/isspace are separate char-taking helpers and are already well defined, so they are untouched, as is is_base64(), which already takes unsigned char.
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
boot or update path
AI analysis · Moderate 51/100
This commit fixes a low-level programming mistake in how Monero handles bytes received from outside the program. Functions that classify characters (like checking if a byte is a space, blank, letter, or digit) were being given bytes that could be interpreted as negative numbers on the systems Monero runs on. That is officially undefined behavior, meaning the program could in theory read out of bounds, crash, or misbeave on some C library implementations. The fix casts those bytes to unsigned char before passing them to the classification functions. The commit message says the bug is quiet in practice on glibc and macOS, but could be a real problem on other C libraries.
In RPC calls `get_blocks.bin` and `get_transactions`: 1. Skip deserializing then re-serializing tx blobs 2. Provide full unpruned transaction from mempool in `get_transactions` when `!req.prune` 3. Change `on_get_transactions()` response sort time from O(N^2) to O(N) 4. Generally improve memory usage and lookups in `on_get_transactions()`
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Low 26/100
This commit is a performance optimization for Monero's RPC endpoints that fetch blocks and transactions. It replaces slow full transaction parsing with a lightweight custom parser, avoids unnecessary re-serialization, and improves how mempool transactions are returned. The changes touch security-relevant code paths (parsing untrusted transaction blobs and deciding what data to expose), but the commit itself is framed as a speedup, not a security fix. There is no direct evidence in the commit message or diff of a vulnerability being fixed, though the new parser could in principle introduce parsing bugs.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 14/100
This commit is a routine performance cleanup. It reserves memory ahead of time for a list of output keys, avoids one unnecessary move of a block object, and reuses a boolean tracking vector instead of recreating it inside a loop. None of these changes alter security behavior or fix a vulnerability.
Security candidatecrypto: check key image in ring signature verifby jeffro256 · 879b09f0 · Aug 27, 2026 · 3 filesMessage 50 · ThinHigh 78Details
Commit message · jeffro256
crypto: check key image in ring signature verif
50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundaryprivacy or spend-authorization protocolcryptography-sensitive path
AI analysis · High 78/100
This Monero patch adds validation checks during ring signature verification to reject certain malformed 'key images.' A key image is a cryptographic fingerprint that proves a coin is being spent without revealing which coin. Before this fix, the verifier accepted some mathematically invalid key images, such as the identity point or points whose order divides a small number (torsioned points). An attacker could potentially craft such a key image to bypass the 'already spent' check, enabling double-spending of coins or denial of service against the network.
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit removes a build-time test that checked whether the Protobuf library could compile and link correctly for Trezor hardware wallet support. It does not change any runtime code that handles user funds, transactions, or network data. The change only affects the build system and removes a compile-time sanity check, so it is not a security vulnerability by itself.
AI review queueddepends: protobuf: don't use android system loggingby tobtoht · cd8beb75 · Aug 26, 2026 · 3 filesMessage 50 · ThinInformational 21Details
Commit message · tobtoht
depends: protobuf: don't use android system logging
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 21/100
This commit changes how Monero's build system handles the protobuf library on Android. It disables protobuf's use of Android's system logging and stops linking the Android 'log' library when building through the project's dependency system. The change appears to be a build-system hardening or compatibility fix, not a patch for an active security vulnerability. There is no direct evidence in the commit that this fixes an exploitable bug.
Initialize RPC server state used by direct handler calls, let fuzz input choose restricted or unrestricted mode, and skip iterations when the dummy core fails to initialize.
Also update the RPC fuzz harness documentation after removal of the old RPC payment setup.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationfuzzing or regression evidence
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
fuzzing or regression evidenceprivacy or spend-authorization protocol
AI analysis · Informational 15/100
This commit only adds a new automated fuzz test for Monero's Bulletproof+ range proof verification code. It does not change any production code, cryptographic logic, or network behavior. There is no indication this commit fixes or introduces a security issue.
Lower-priorityfcmp_pp_rust: build with cargo --lockedby Thomas · 683f539a · Aug 26, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Thomas
fcmp_pp_rust: build with cargo --locked
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Low 42/100
This commit fixes two memory-safety bugs in Monero's command-line blockchain utility tools. One bug could let a crafted saved state file cause the program to allocate an enormous vector and crash or exhaust memory. The other bug could cause the program to read a transaction input incorrectly and crash when computing ring-size statistics. These are offline analysis tools, not the live Monero daemon or wallet, so they do not directly affect running nodes or user funds.
Lower-priorityrpc, common: remove dead codeby Thomas · 9dc5cf51 · Aug 25, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Thomas
rpc, common: remove dead code
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body