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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityreadme: line break between copyright headersby tobtoht · b6a29b0a · Aug 14, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · tobtoht
readme: line break between copyright headers
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedfunctional_tests_rpc: fix string.join()by a9oss · e000d42a · Aug 14, 2026 · 1 fileMessage 35 · OpaqueInformational 16Details
Commit message · a9oss
functional_tests_rpc: fix string.join()
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 16/100
This is a tiny Python 2-to-3 compatibility fix in a test helper script. It changes an outdated way of joining a list of strings into a modern one. The script only prints a help message listing available tests, so the change has no security relevance and does not affect the Monero wallet, daemon, or any user funds.
Security candidatecryptonote_basic: parse_and_validate_tx param to check max sizeby j-berman · 236ca60b · Aug 13, 2026 · 7 filesMessage 85 · StrongModerate 63Details
Commit message · j-berman
cryptonote_basic: parse_and_validate_tx param to check max size
Simple API to check max blob size before parsing. This is useful when reading blobs from untrusted sources.
@selsta pointed out that coinbase txs can technically be larger than get_max_tx_size(), otherwise we could enforce it on all 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
defensive validationcryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Moderate 63/100
This Monero commit adds an optional size check to transaction parsing functions so that oversized transaction blobs from untrusted network sources are rejected before being decoded. It is a defensive hardening change that consolidates existing size checks and extends them to more code paths, reducing the chance that a maliciously large blob could waste resources or trigger memory-related issues during parsing.
Lower-priorityfunctional_tests: remove unreachable code, kill process after timeoutby SNeedlewoods · a16b3c80 · Aug 13, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · SNeedlewoods
functional_tests: remove unreachable code, kill process after timeout
Co-authored-by: selsta <selsta@sent.at>
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritycmake: enable compiler caching support for rust librariesby jpk68 · 67d99a98 · Aug 12, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · jpk68
cmake: enable compiler caching support for rust libraries
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedsimplewallet: don't ignore misplaced index= in sweep commandsby jpk68 · 6bc69dd5 · Aug 12, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · jpk68
simplewallet: don't ignore misplaced index= in sweep commands
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 35/100
This change fixes a bug in Monero's command-line wallet (simplewallet) where a user typing 'index=' in the wrong position of a 'sweep' command could be silently ignored. Previously, the wallet only checked the very first word for 'index='; if it appeared later, the wallet would act as if no subaddress index was specified, potentially sweeping funds from unintended addresses. The fix scans all words for 'index=' and removes it when found. This is primarily a usability/transaction-safety bug rather than a remote-exploitable vulnerability.
AI review queuedfcmp_pp_rust: fix docker buildby tobtoht · 6f9c5828 · Aug 12, 2026 · 1 fileMessage 35 · OpaqueInformational 16Details
Commit message · tobtoht
fcmp_pp_rust: fix docker build
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This is a build-system patch that lets the Rust part of Monero compile correctly when targeting Linux systems that use the lightweight 'musl' C library (common in Docker containers). It adds a check so the build picks the right Rust toolchain variant. There is no indication this changes any runtime behavior, cryptographic logic, or network code.
Lower-prioritydepends: set CMAKE_{LANG}_COMPILER_TARGETby tobtoht · 1d909d09 · Aug 12, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · tobtoht
depends: set CMAKE_{LANG}_COMPILER_TARGET
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityrpc, p2p: remove pay-to-use RPC leftoversby Thomas · 67764f67 · Aug 12, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Thomas
rpc, p2p: remove pay-to-use RPC leftovers
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatetx_pool: do expensive verify after potential no-drop offensesby j-berman · 41e06a1b · Aug 11, 2026 · 1 fileMessage 60 · AdequateLow 48Details
Commit message · j-berman
tx_pool: do expensive verify after potential no-drop offenses
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
cryptography-sensitive path
AI analysis · Low 48/100
This commit changes the order in which Monero checks incoming transactions. Instead of running an expensive consensus check first, it now checks cheaper 'no-drop' rules (like whether the transaction pays a valid fee and isn't already known) before doing the heavy validation. This is a performance and resource-usage optimization, likely to reduce denial-of-service risk from spam transactions. A second small change makes the spent-key-image check skip non-standard input types instead of asserting they never occur. The commit message and diff do not describe this as a security fix, and no independent researcher is credited.
Lower-prioritycheckpoints: exclude equal height in get_nearest_checkpoint_heightby woodser · 18472932 · Aug 11, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · woodser
checkpoints: exclude equal height in get_nearest_checkpoint_height
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedwallet2: keep multisig import state consistent across failed refreshesby woodser · 354906f1 · Aug 11, 2026 · 1 fileMessage 50 · ThinLow 33Details
Commit message · woodser
wallet2: keep multisig import state consistent across failed refreshes
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 33/100
This change fixes a bug in Monero's multisig wallet import process. Previously, if importing multisig data failed partway through, the wallet could be left with a mix of old and new internal state, potentially causing confusion or incorrect behavior on the next import attempt. The patch now validates all incoming data in a temporary staging area and only replaces the wallet's live state after everything checks out, keeping things consistent even when something goes wrong.
Seed connections bypassed the existing failed-address cache, causing unreachable or rejected seeds to be retried repeatedly.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Low 39/100
This patch fixes a bug in Monero's peer-to-peer networking code. Previously, when the software tried to connect to 'seed nodes' (hardcoded first-contact servers that help a node find the network), it ignored the cache of recently-failed addresses. That meant an unreachable or rejecting seed node could be retried over and over again, wasting resources and potentially delaying or preventing a node from successfully joining the Monero network. The fix makes seed-node connections respect a shorter 5-minute 'cooldown' before retrying a failed seed, while normal peer connections keep the existing 1-hour cooldown.
AI review queuedsimplewallet: reject donations when not on mainnetby jpk68 · 773e3070 · Aug 11, 2026 · 1 fileMessage 50 · ThinLow 32Details
Commit message · jpk68
simplewallet: reject donations when not on mainnet
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 32/100
This change stops the Monero command-line wallet's built-in 'donate' command from working on test networks. Previously, the wallet tried to convert the official donation address to a testnet/stagenet equivalent, which could send real-looking donations to an address the user did not expect. Now it simply refuses to donate unless you are on the main Monero network.
AI review queuedwallet_rpc_server: expose change amount in transfer entriesby SlowBearDigger · d7f32ed8 · Aug 11, 2026 · 3 filesMessage 50 · ThinInformational 19Details
Commit message · SlowBearDigger
wallet_rpc_server: expose change amount in transfer entries
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 'change_amount' field to Monero wallet RPC responses that describe transfers. When you send Monero, part of the input often comes back to you as change. Previously, callers of the wallet RPC had to calculate this themselves from other fields; now it is exposed directly. This is a straightforward feature addition, not a security fix or vulnerability.
✓ Specific, descriptive subject! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 59/100
This commit refactors how Monero checks whether a new block's timestamp is valid. It splits one timestamp-check function into two: a general helper and one specifically for the main chain. The change also moves the 'future time' check (rejecting blocks stamped more than 2 hours ahead of local time) and the 'not enough blocks' check into the general helper, and it makes the median timestamp output optional. The commit appears to be a code-quality and consistency improvement rather than a clear-cut security fix, but it does tighten behavior when there are fewer than 60 prior blocks and removes a const qualifier from one function. Without a vendor statement, we cannot say it fixes a known vulnerability.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritydaemon: add unban all commandby Rene Guenon · 4b3eabf8 · Aug 11, 2026 · 6 filesMessage 45 · ThinTriage 0Details
Commit message · Rene Guenon
daemon: add unban all command
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedDockerfile: add rustby tobtoht · 23dfb88f · Aug 11, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · tobtoht
Dockerfile: add rust
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply adds the Rust programming language toolchain to the project's Docker build environment. It is a routine build-infrastructure change with no apparent security relevance.
AI review queuedp2p: don't reset timeout timer for handshakesby j-berman · 7e0c68b4 · Aug 11, 2026 · 1 fileMessage 68 · AdequateLow 49Details
Commit message · j-berman
p2p: don't reset timeout timer for handshakes
The handshake timeout should just be an absolute timeout, we don't care about partial messages received during the handshake.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 49/100
This change fixes a peer-to-peer networking timeout behavior. Previously, the handshake timeout timer could be reset by incoming partial data, potentially allowing a remote peer to drag out the handshake indefinitely. Now, the handshake timeout is absolute: if it expires, the connection is dropped regardless of partial progress. This prevents a likely denial-of-service vector where a malicious or slow peer stalls handshakes.
✓ Specific, descriptive subject! No meaningful explanatory body
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Informational 15/100
This commit only adds the C++ keyword `static` to a single function declaration in a header file. It does not change what the function does, what data it can access, or how users interact with the software. There is no visible security effect.