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.
51/100 average clarity
20Strong · 80–100
123Adequate · 60–79
534Thin · 40–59
66Opaque · 0–39
14security candidates with opaque commit messaging
This Monero wallet update fixes a bookkeeping bug. When a wallet imported a list of its owned outputs and that list was smaller than a previous import, internal lookup maps (key images and public keys) could still point to entries that no …
Internal index/cache consistency fix in wallet output handlingPrevents out-of-range references after transfer list resizeAdds defensive repair on wallet cache load for unrefreshed wallets
This commit simplifies how Monero's simplewallet decides whether a payment ID is a real encrypted ID or a dummy placeholder. Previously, the wallet checked both the payment ID value and whether any destination was an integrated address, an…
Removal of a CHECK_AND_ASSERT_MES consistency check between destination flags and payment ID valueChange from dual-factor classification (address type + payload) to payload-only classificationPotential for previously rejected transactions to be accepted if the old check was overly strict
This Monero wallet patch cleans up internal lookup tables (key-image and public-key indexes) when the list of owned transaction outputs is shrunk, for example during an output import. Without the cleanup, those indexes could point to entri…
Out-of-bounds index retained in wallet lookup maps after container shrinkPotential wallet crash or incorrect spend selection due to stale key-image / public-key mappingRepair-on-load for legacy wallet caches that predate the fix
This small change removes a consistency check in Monero's command-line wallet when loading a saved transaction. Previously, the wallet verified that a 'dummy' payment ID label matched a special zero-value payment ID. Now it labels the paym…
Removal of a CHECK_AND_ASSERT_MES consistency checkRemoval of integrated-address validation for payment ID classificationChange in UI/labeling logic for loaded transactions
This commit updates Monero's built-in blockchain checkpoints to match the v0.18.5.3 release. Checkpoints are hard-coded reference points that help nodes quickly verify they are following the correct chain and resist certain attacks. The ch…
Hard-coded blockchain checkpoint data updated to a newer height/hashExpected compiled-in block hashes digest changedNo new code paths, cryptographic changes, or bug fixes visible in the diff
This is a small code fix in Monero's wallet that keeps the recorded breakdown of received amounts consistent when a transaction output is 'burnt' (replaced or spent as part of a transaction the wallet is processing). The change adds a chec…
Defensive consistency check added (THROW_WALLET_EXCEPTION_IF)Fixes internal accounting of received output amountsNo explicit security claim in commit or supplied references
This patch fixes a spot in the Monero wallet where an untrusted remote server (daemon) could supply a misleading 'status' field. Previously, the wallet used that raw status directly in its error handling, which could potentially make a mal…
Untrusted input from remote daemon used in error-handling pathMissing trust check on daemon-reported RPC statusSingle-call-site hardening patch
This commit adds two new read-only options to the wallet's remote procedure call (RPC) interface so users can request their public view key and public spend key. Public keys are meant to be shared openly and are not secrets, so exposing th…
This commit only updates a submodule pointer for the external polyseed library from one commit hash to another. The actual code changes inside the submodule are not shown in the diff, and no public references were supplied. There is no vis…
This patch fixes a size-limit accounting bug in Monero's built-in HTTP server. When a client sends multiple HTTP requests back-to-back on the same connection (pipelining), leftover buffered data from the next request was not being counted …
Request size limit bypass via pipelined HTTP cachingDenial-of-service / memory pressure potential from oversized requestsFix in low-level network protocol handler
This patch fixes a privacy leak in Monero's wallet RPC server. Previously, the --no-dns flag was ignored when no wallet was loaded, so the validate_address RPC call could still perform a DNS lookup (OpenAlias) even though the user had expl…
Privacy leak: RPC ignored --no-dns when no wallet loadedDNS lookup performed despite explicit user opt-outOpenAlias resolution could disclose queried addresses/aliases to DNS resolvers
This commit adds cleanup of three additional memory buffers in Monero's seed-phrase key-stretching code. Before the change, leftover copies of intermediate secrets could remain in stack memory after the function finished. An attacker who c…
Sensitive intermediate key material left in stack memory after function returnUse of sodium_memzero to clear cryptographic buffersPBKDF2 implementation handling mnemonic-derived secrets
This update improves the Monero wallet's command that connects to a network node (daemon). It lets users supply a username/password and a proxy address when switching daemons, and it replaces an older one-step connection method with a newe…
Added mutex lock in wallet2::set_proxy to protect concurrent access to proxy and HTTP client stateset_daemon now passes RPC login credentials and proxy settings through the proper wallet2::set_daemon APITrust heuristic changed to only auto-trust local daemons when no proxy is in use
This change alters how Monero creates a view-only wallet copy. Previously, the code exported outputs using a method that could strip some metadata. Now it copies the full internal transfer records directly, then wipes and clears the multi-…
Sensitive field sanitization before export (memwipe + clear of m_multisig_k)Change in data export path for view-only wallet creationPreservation of 'complete output metadata' implying previous path was incomplete
This Monero update hardens how public keys and transaction pubkeys are handled. It moves a low-level 'torsion clearing' routine into the core crypto library, adds checks that wallet/destination addresses are valid points on the main subgro…
Adds main-subgroup membership validation for public address keys (spend/view)Normalizes transaction public keys before use in payment-ID decryption and tx proofsMoves torsion-clearing primitive into core crypto layer to ensure consistent behavior
This Monero update fixes a networking bug where the server could accidentally block all of its worker threads while waiting for slow clients to accept data. If all workers became stuck this way, the node could stop processing any network t…
Removal of blocking condition-variable wait in network send pathFail-fast on send-queue overflow instead of parking worker threadsHTTP handler now propagates send failures and enters error state
This Monero wallet patch adds stronger safety checks when a wallet prepares, signs, or loads multi-step transactions (unsigned transactions, multisig transactions, and cold-device transactions). It verifies that money going into the transa…
Adds duplicate-input detection across transaction setsAdds destination address type consistency checksAdds uint64 overflow guard for summed input amounts
This Monero update makes the network layer clean up leftover block download records when a peer connection fails or is rejected. Previously, rejected or disconnected peers could leave stale block spans in a queue, which might cause the nod…
Denial-of-service resistance: stale block spans from malicious or faulty peers could prevent a node from obtaining valid blocksState cleanup on peer disconnection/rejectionNo authentication or memory-safety bug evident in diff
This small patch fixes a bug in the Monero wallet where, if an output had already been scanned once, the wallet would return early without clearing an error flag. In rare cases this could leave a stale 'error' state attached to a transacti…
Stale error-state propagation in wallet scanning logicMissing reset of tx_scan_info.error on cached/short-circuit code pathPotential for incorrect received-payment or scan-failure reporting
This change fixes a binary search in the Monero wallet that previously could loop forever or behave incorrectly if something went wrong. The old code used an unbounded 'while (true)' loop and a midpoint calculation that could overflow. The…
Unbounded loop replaced with bounded iterationInteger overflow mitigation in midpoint calculationDefensive error handling added for search failure
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityrelease: drop support for arm32 linuxby tobtoht · c3ee9ac7 · Nov 1, 2025 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · tobtoht
release: drop support for arm32 linux
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedfuzz: fix some warningsby jeffro256 · 32d9359b · Oct 28, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · jeffro256
fuzz: fix some warnings
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
fuzzing or regression evidencesecond-pass: opaque commit message
AI analysis · Informational 15/100
This commit only cleans up compiler warnings in test/fuzzing code. It changes some integer variable types from signed to unsigned and removes an unused variable. There is no change to the live Monero node or wallet code that users run, and nothing here affects real funds, privacy, or network security.
Lower-priorityblockchain_prune: check DB versionby jeffro256 · 9e57f9be · Oct 27, 2025 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · jeffro256
blockchain_prune: check DB version
Prevents accidental future corruption of the database by refusing to prune the DB before checking the version value inside the properties table.
AI review queuedwallet: sanity check ring indices only against spendableby jeffro256 · 5905b202 · Oct 15, 2025 · 1 fileMessage 50 · ThinLow 44Details
Commit message · jeffro256
wallet: sanity check ring indices only against spendable
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 44/100
This commit tightens a sanity check in the Monero wallet when it selects decoy ring members for a transaction. Previously, the wallet compared selected outputs against the total number of recently confirmed outputs (the top of the 'rct_offsets' list). Now it compares against only outputs old enough to be considered spendable. This avoids incorrectly rejecting valid transactions or, potentially, accepting risky ones when the very newest outputs are not yet spendable. The change is small and defensive.
Lower-priorityepee: align container pod as blob serializationby jeffro256 · ece0342c · Oct 14, 2025 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · jeffro256
epee: align container pod as blob serialization
`{un}serialize_stl_container_pod_val_as_blob()` use aligned memory accesses on potentially unaligned pointers.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Security candidateBlockchainDB: rm `skip_coinbase` in `get_blocks_from()`by jeffro256 · a863bf70 · Oct 13, 2025 · 5 filesMessage 73 · AdequateInformational 18Details
Commit message · jeffro256
BlockchainDB: rm `skip_coinbase` in `get_blocks_from()`
Parameter `skip_coinbase` was always set to `true`, and didn't actually skip the coinbase transactions. The method broke when set to `false`.
Noticed by @akildemir
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
proof-of-work or emission validationcryptography-sensitive path
AI analysis · Informational 18/100
This is a small code cleanup, not a security fix. A database function had a 'skip coinbase' option that was always turned on and didn't actually work when turned off. The patch removes the broken, unused option entirely. The only caller kept using the same behavior, so nothing changes for users.
AI review queuedadd getter for daemon proxyby woodser · e87eecf8 · Oct 12, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · woodser
add getter for daemon proxy
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 adds a simple read-only accessor (getter) method that returns the wallet's configured proxy address. It does not change any behavior, fix any bug, or alter how data is handled. There is no security issue visible in this change.
When the request includes block_ids, the daemon uses find_blockchain_supplement to identify the highest block hash passed in block_ids that the daemon also knows about, and then serves subsequent blocks contiguous to that block.
When block_ids_skip_exclusive is false (default current behavior), the daemon includes the highest block requested in the response, in addition to contiguous blocks after it.
When block_ids_skip_exclusive is true (new param), the daemon serves blocks starting from the block 1 higher than the highest known block included in block_ids. Thus, the daemon skips the common block known to the client and daemon. Clients can make sure the daemon is serving expected contiguous blocks to its highest known block by checking the first block's prev_id included in the response, and making sure it is equivalent to the block the client already knows about that was included in block_ids. This avoids the daemon serving 1 extra block it does not need to serve to the client, since the client should already know about that block.
bl
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Informational 24/100
This commit adds a new optional flag to the Monero daemon's binary RPC for fetching blocks. When enabled, the daemon skips sending the one block the client already knows about, reducing bandwidth. The change is backward-compatible (default is the old behavior) and appears to be a routine protocol optimization, not a security fix.
cryptonote_core: rm confusing/redundant BP consensus rule
This rule is confusing/redundant because before v8, no bulletproofs whatsoever were allowed. And during and after v8, ONLY multi-output bulletproofs were allowed, i.e. exactly 1 bulletproof is allowed which proves the range of all amount commitments in the transaction.
Sources: * No BP before v8: - https://github.com/monero-project/monero/blob/d32b5bfe18e2f5b979fa8dc3a8966c76159ca722/src/cryptonote_core/blockchain.cpp#L3021-L3032 * Only 1 BP allowed: - https://github.com/monero-project/monero/blob/d32b5bfe18e2f5b979fa8dc3a8966c76159ca722/src/cryptonote_basic/cryptonote_format_utils.cpp#L174 - https://github.com/monero-project/monero/blob/d32b5bfe18e2f5b979fa8dc3a8966c76159ca722/src/cryptonote_basic/cryptonote_format_utils.cpp#L150 * BP must cover all outputs: - https://github.com/monero-project/monero/blob/d32b5bfe18e2f5b979fa8dc3a8966c76159ca722/src/cryptonote_basic/cryptonote_format_utils.cpp#L190-L194 - https://github.com/monero-project/monero/blob/d32b5bfe18e2f5b979fa8dc3a8966c76159ca722/src/cryptonote_basic/cryptonote_format_utils.cpp#L166-L170
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
consensus or confidential-proof validationprivacy or spend-authorization protocolcryptography-sensitive path
AI analysis · Informational 12/100
This commit removes a redundant safety check in Monero's transaction validation code. The commit message argues the check was unnecessary because other rules already enforce the same limits: no bulletproofs before protocol version 8, and only one bulletproof covering all outputs from version 8 onward. The change is presented as cleanup, not a security fix.
AI review queueddepends: explicitely set C/CXX standard for all packagesby tobtoht · 3a8937a0 · Oct 8, 2025 · 10 filesMessage 50 · ThinInformational 19Details
Commit message · tobtoht
depends: explicitely set C/CXX standard for all packages
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 19/100
This commit standardizes which C and C++ language versions are used when building Monero's external dependencies across all supported platforms. It sets a default of C11 and C++17, applies those defaults consistently to Android, macOS, FreeBSD, Linux, and Windows builds, and removes duplicate version flags from individual package recipes. The change is a build-system hardening and consistency improvement, not a fix for a known exploitable vulnerability.
Lower-prioritydepends: openssl: update to 3.5.4by tobtoht · 335fb0b2 · Oct 8, 2025 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · tobtoht
depends: openssl: update to 3.5.4
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityCoC: Maintainers should not merge patches that have unaddressed commentsby tobtoht · 6f65c51d · Oct 8, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · tobtoht
CoC: Maintainers should not merge patches that have unaddressed comments
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityCoC: do not dictate how a Contributor should work on an issueby tobtoht · 6a8102c0 · Oct 8, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · tobtoht
CoC: do not dictate how a Contributor should work on an issue
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
This commit removes an introductory 'Goals' section from the project's contributor documentation (docs/CONTRIBUTING.md). It is a pure documentation edit with no code changes, no configuration changes, and no security relevance.
8d6855c CoC: only allow Administrators to merge changes to the CoC (tobtoht)
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a large repository initialization or merge that adds the entire Monero codebase, build files, documentation, tests, and GitHub CI configuration. The only functional code change explicitly described in the merge message is a governance rule for the Code of Conduct: only GitHub Administrators are allowed to merge changes to it. There is no indication of a security bug fix or vulnerability patch in the supplied materials.