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.
This commit removes a former Monero maintainer's GPG key from the list of trusted keys used by the GUI wallet's automatic updater. It is a routine trust-list cleanup after a maintainer left the project, not a fix for an active security fla…
Removal of a trusted GPG key from the software-update trust anchor setChange affects the built-in GUI updater's maintainer verification list
This commit adds a new command-line option --ssl-check and runs it in CI. The check makes a simple HTTPS request to the Monero website to confirm SSL/TLS certificate validation is working in the build. It is a testing/diagnostic addition, …
Adds SSL/TLS connectivity self-testUnsets SSL_CERT_FILE/SSL_CERT_DIR in CI to test default certificate validation pathHidden CLI option not exposed in help
This commit changes the macOS build instructions to install a specific, pinned version of OpenSSL (version 3) rather than whatever the latest version happens to be. It also tells the build system exactly where that pinned version is locate…
Pins a critical cryptographic dependency (OpenSSL) to a known major versionAdds explicit OPENSSL_ROOT_DIR to prevent CMake from picking up an unintended OpenSSL installationReduces supply-chain risk from unpinned Homebrew formula updates
This merge changes how text is shown in the Monero GUI wallet. The main goal appears to be preventing rich-text formatting (HTML-like markup) from being interpreted in places where untrusted data could appear, such as scanned QR codes, dia…
Multiple QML text elements switched from AutoText/default to Text.PlainTextStandardDialog content area defaulted to TextEdit.PlainText instead of TextEdit.AutoTextQRCodeScanner removed MessageDialog usage and routes errors through informationPopup
This commit adds a new automated test that runs in the project's continuous integration (CI) pipeline. The test launches the Monero GUI wallet with a hidden '--ssl-check' flag, which tries to download a small file over HTTPS from the offic…
New hidden CLI flag added for SSL/TLS connectivity validationCI runs SSL check against real external endpoint (web.getmonero.org)Environment variables SSL_CERT_FILE and SSL_CERT_DIR are explicitly unset during CI test to ensure bundled certificates are used
This commit changes the macOS build instructions in an automated workflow so that the build explicitly uses OpenSSL version 3 instead of whatever version Homebrew currently provides by default. It is a build-hardening change, not a fix for…
Dependency version pinning in CI/CD workflowExplicit OPENSSL_ROOT_DIR to avoid picking up a different OpenSSL installationBuild reproducibility / supply-chain hardening
This is a small user-interface improvement for the Monero GUI wallet. When a user checks a 'reserve proof' (a cryptographic receipt showing how much Monero an address holds), the result popup now also shows the unspent amount. The code als…
No security-relevant signal: UI-only change adding an unspent amount label to reserve proof checksDefensive initialization of local output variables (good=false, total=0, spent=0), which is good practice but not a fix for an observed bug
This update fixes how the Monero GUI reads OpenPGP public keys. Previously, the software might have accepted a revoked (cancelled) subkey, or used an older signature that allowed signing even when a newer one did not. The patch now rejects…
OpenPGP subkey revocation not previously enforcedBinding signature selection did not consider creation time, allowing stale signing-capable signatures to override newer non-signing onesMarker/Trust packets now skipped without terminating subkey signature sequence
This commit updates the Monero GUI's message/file signing feature so users can now sign with any wallet subaddress, not just the main address. It also disables signing for hardware-backed and view-only wallets, shows clearer error messages…
Signing now bound to a user-selected wallet address/subaddress, reducing risk of signing under an unintended primary addressHardware-backed and view-only wallets are explicitly prevented from signing in the UIError handling added for failed sign operations
This is a user-interface performance patch for the Monero wallet app. It rewrites how the Account and Receive pages display long lists of subaddresses, replacing a layout that loaded every item at once with a scrollable list that reuses it…
No direct security signal in diff: no cryptographic, network, or wallet-seed handling changesOne defensive guard added: bounds check on subaddressListView.currentIndex before accessing wallet subaddress dataOne variable rename fixes a typo but has no security effect
This commit is a minor user-interface improvement for the Monero GUI wallet. When a user checks a 'reserve proof' (a cryptographic attestation about how much Monero is held and spent), the result dialog now also shows the 'unspent' amount.…
This change fixes how the Monero GUI reads OpenPGP public keys. Previously, the software might accept a revoked (cancelled) subkey or use an older signature that allowed signing even when a newer one did not. After the patch, revoked subke…
OpenPGP subkey revocation now enforcedBinding signature selection changed from first-match to newest-by-creation-timeMarker and Trust packets now explicitly skipped without terminating subkey signature sequence
This commit changes how the Monero wallet's user interface displays text that comes from outside sources. It switches several labels and dialogs from rich text (which can include formatting, links, or hidden instructions) to plain text, re…
Multiple QML text elements switched from AutoText/RichText-capable defaults to Text.PlainTextStandardDialog default textFormat changed from TextEdit.AutoText to TextEdit.PlainTextQR scanner MessageDialog removed; scanned data errors now shown through a controlled popup as plain text
This commit updates the Monero GUI wallet's signing feature so users can now sign messages and files using any wallet subaddress, not just the main address. It also disables signing for hardware-backed and view-only wallets, shows clearer …
Signing UI now disabled for hardware-backed wallets (isHwBacked) and view-only wallets (viewOnly)Backend error strings are now displayed to the user instead of silently failingForeign / non-wallet addresses are rejected by the underlying wallet implementation and produce an error dialog
This commit only updates the version pointer of an embedded dependency called 'quirc' (a QR-code decoding library) inside the Monero GUI repository. The actual code changes are not shown in the diff because the dependency is stored as a se…
This change tightens how the Monero GUI wallet handles its network proxy settings. Previously, the wallet's proxy address could be changed from many places in the app, which could let a bug or malicious UI flow silently switch traffic to a…
Removal of writable proxy address setter reduces attack surface for proxy misconfigurationCentralizes proxy reconnection logic in a single helper functionPrevents QML binding from silently overriding proxy address
This change hardens how the Monero GUI opens a printable PDF seed template. Previously, the app copied a bundled PDF to a predictable temporary path and opened it without checking whether the file had been tampered with. Now it creates a p…
Local file integrity verification added (SHA-256) before opening an embedded PDFPredictable temporary file path replaced with QTemporaryDir unique directoryReturn-value handling added so QML can surface verification failures to the user
This patch fixes a user-interface freeze in the Monero GUI wallet when using the 'sweep unmixable outputs' feature. The old code called a synchronous (blocking) function that could hang the interface; the new code uses an asynchronous call…
UI freeze / denial-of-service to the local user when sweeping unmixable outputsObject lifetime change in PendingTransaction parent assignmentNo input validation, cryptographic, or network security changes visible
This commit is a large cleanup and hardening of the OpenPGP signature verification code used by the Monero GUI's automatic updater. It adds stricter parsing of armored PGP data, validates armor headers and checksums, rejects unexpected sig…
Custom cryptographic code was significantly hardenedSignature verification now rejects unsupported signature typesArmor parsing now validates headers, tails, base64 alphabet, and CRC24
This commit is a user-interface cleanup, not a security fix. It moves the existing password-strength meter into a reusable component and adds it to the password-change dialog. The actual password-strength calculation is still performed by …
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Informational 22/100
This commit removes a former Monero maintainer's GPG key from the list of trusted keys used by the GUI wallet's automatic updater. It is a routine trust-list cleanup after a maintainer left the project, not a fix for an active security flaw. There is no evidence in the commit that any malicious update was actually signed or distributed.
This commit changes the macOS build instructions to install a specific, pinned version of OpenSSL (version 3) rather than whatever the latest version happens to be. It also tells the build system exactly where that pinned version is located. This is a supply-chain and build-reliability hardening change: it reduces the chance that a future, incompatible, or unexpectedly vulnerable OpenSSL update breaks the build or gets bundled into Monero GUI releases without review.
d68890a qml: show untrusted text as plain text (jpk68)
ACKs: selsta
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 61/100
This merge changes how text is shown in the Monero GUI wallet. The main goal appears to be preventing rich-text formatting (HTML-like markup) from being interpreted in places where untrusted data could appear, such as scanned QR codes, dialog boxes, and transaction details. It also adds a new transaction-details popup that explicitly uses rich text. The change reduces the risk that an attacker could trick the wallet into displaying fake instructions or clickable links by embedding markup in data the wallet reads.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controldocumentation-only discount
AI analysis · Informational 17/100
This commit changes the macOS build instructions in an automated workflow so that the build explicitly uses OpenSSL version 3 instead of whatever version Homebrew currently provides by default. It is a build-hardening change, not a fix for an active software bug. The change reduces the risk that a future Homebrew update to a newer or incompatible OpenSSL version silently breaks the build or changes the cryptographic behavior of the released macOS application.
7fa384f openpgp: reject revoked subkeys and use newest binding signature (jpk68)
ACKs: selsta
56/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarymerge-commit duplicate discount
AI analysis · High 72/100
This update fixes how the Monero GUI reads OpenPGP public keys. Previously, the software might have accepted a revoked (cancelled) subkey, or used an older signature that allowed signing even when a newer one did not. The patch now rejects revoked subkeys and picks the most recent binding signature. This prevents an attacker who controls an old or revoked OpenPGP subkey from tricking the wallet into treating it as valid for signing.
eeaa861 sign: support signing with wallet subaddresses (Samy)
ACKs: jpk68, selsta
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryprivacy or spend-authorization protocolsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 32/100
This commit updates the Monero GUI's message/file signing feature so users can now sign with any wallet subaddress, not just the main address. It also disables signing for hardware-backed and view-only wallets, shows clearer error messages, and adds tests. There is no direct evidence this is a security fix for an active vulnerability; it reads as a feature enhancement with defensive hardening.
78331af qml: improve performance with many subaddresses (selsta)
ACKs: jpk68
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolmerge-commit duplicate discount
AI analysis · Informational 19/100
This is a user-interface performance patch for the Monero wallet app. It rewrites how the Account and Receive pages display long lists of subaddresses, replacing a layout that loaded every item at once with a scrollable list that reuses items. There is no clear security bug being fixed; it appears aimed at making the app faster and smoother when many addresses exist.
Security candidateopenpgp: reject revoked subkeys and use newest binding signatureby jpk68 · 7fa384fa · Nov 8, 2026 · 2 filesMessage 55 · ThinModerate 61Details
Commit message · jpk68
openpgp: reject revoked subkeys and use newest binding signature
55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Moderate 61/100
This change fixes how the Monero GUI reads OpenPGP public keys. Previously, the software might accept a revoked (cancelled) subkey or use an older signature that allowed signing even when a newer one did not. After the patch, revoked subkeys are rejected and only the newest valid binding signature is used to decide whether a subkey can sign. This prevents an attacker who controls an OpenPGP key file from tricking the wallet into trusting a subkey that should not be trusted.
Security candidateqml: show untrusted text as plain textby jpk68 · d68890af · Nov 8, 2026 · 8 filesMessage 45 · ThinModerate 65Details
Commit message · jpk68
qml: show untrusted text as plain text
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Moderate 65/100
This commit changes how the Monero wallet's user interface displays text that comes from outside sources. It switches several labels and dialogs from rich text (which can include formatting, links, or hidden instructions) to plain text, reducing the risk that an attacker could trick the wallet into showing a fake message or clickable link. It also replaces a system message dialog in the QR scanner with a custom one so scanned QR code data is not rendered as rich text. A new transaction-details popup is intentionally kept as rich text, but only for wallet-generated transaction summaries.
Security candidatesign: support signing with wallet subaddressesby Samy · eeaa8617 · Nov 4, 2026 · 4 filesMessage 45 · ThinLow 32Details
Commit message · Samy
sign: support signing with wallet subaddresses
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundaryprivacy or spend-authorization protocolsigning or wallet path
AI analysis · Low 32/100
This commit updates the Monero GUI wallet's signing feature so users can now sign messages and files using any wallet subaddress, not just the main address. It also disables signing for hardware-backed and view-only wallets, shows clearer error messages, and adds tests. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be a feature and hardening improvement.
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 57/100
This commit is a large cleanup and hardening of the OpenPGP signature verification code used by the Monero GUI's automatic updater. It adds stricter parsing of armored PGP data, validates armor headers and checksums, rejects unexpected signature types, properly initializes the cryptographic library, and fixes parsing of signed hash files. These changes reduce the chance that a fake or tampered update could be accepted, but the commit itself is described by the project only as 'fix some fragile code' rather than as a security fix.
1ef157f qml: add reusable password strength bar (EntropyHoover)
ACKs: jpk68, selsta
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
entropy or randomnesssigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a user-interface cleanup, not a security fix. It moves the existing password-strength meter into a reusable component and adds it to the password-change dialog. The actual password-strength calculation is still performed by the same backend function as before, and no new behavior that would create or fix a security issue is visible in the diff.
Security candidateopenpgp: fix some fragile codeby jpk68 · 1b36fbe0 · Oct 14, 2026 · 10 filesMessage 45 · ThinHigh 71Details
Commit message · jpk68
openpgp: fix some fragile code
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · High 71/100
This commit rewrites the OpenPGP signature verification code used by the Monero GUI's automatic updater. The changes add stricter parsing of PGP armor, enforce that subkeys used for verification are actually allowed to sign data, reject unexpected signature types, and fix several fragile coding patterns. Because this code protects the update-download path, any weakness here could let an attacker trick the wallet into installing a malicious update. The patch appears to be a hardening/correctness fix rather than a simple refactor, but the commit message does not call it a security fix and no advisory is supplied.
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathsigning or wallet pathboot or update pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 18/100
This is a large routine update that migrates the Monero GUI wallet from Qt 5 to Qt 6. It changes build scripts, packaging Dockerfiles, QML user-interface files, and C++ source to work with the newer Qt version. There is no direct evidence in the commit that this fixes a specific security vulnerability; it appears to be a framework upgrade for compatibility and maintainability. The main security-relevant side effect is that the build now uses newer toolchain versions (NDK, SDK, CMake, Qt) and removes some old Qt 5-specific workarounds.
10b08b3 Wallet: keep daemon credentials scoped to each connection (selsta)
ACKs: jpk68, plowsof, PyXMR2025
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege statesigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 35/100
This change adjusts how the Monero GUI wallet stores and passes login credentials for remote daemon connections. Previously, daemon username/password and 'trusted daemon' status were kept as persistent properties on the wallet object and reused across connections. The patch scopes those credentials to each individual connection instead, passing them as parameters when initializing a connection rather than storing them on the wallet. This reduces the risk that credentials or trust settings from one remote node could accidentally be reused for a different node later.
Wallet: keep daemon credentials scoped to each connection
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege statesigning or wallet path
AI analysis · Low 34/100
This commit changes how the Monero GUI wallet stores and uses login credentials for remote nodes (servers that help the wallet talk to the Monero network). Previously, the wallet kept daemon username/password as persistent wallet-level settings. Now those credentials are passed fresh each time a connection is initialized, so they are scoped to that specific connection instead of lingering on the wallet object. This is a defensive cleanup that reduces the risk of credentials being reused for the wrong node or leaking across connections, but the commit message does not frame it as a security fix.
Security candidateupdater: use proxy for signed hash downloadsby selsta · 5e5ea68f · Aug 23, 2026 · 7 filesMessage 45 · ThinModerate 59Details
Commit message · selsta
updater: use proxy for signed hash downloads
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Moderate 59/100
This change fixes a privacy leak in the Monero GUI wallet's update checker. Previously, when the wallet checked for updates and downloaded the signed list of official file hashes, it did not route that request through the user's configured proxy. This could expose the user's real IP address to the update server and any network observer, even if the user had set a proxy for other wallet traffic. The patch now passes the configured proxy address through to the update check so those hash downloads also go through the proxy.
Transfer: disable offline signing for 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 boundary
AI analysis · Moderate 58/100
This commit removes the 'Sign (offline)' button for hardware wallets in the Monero GUI wallet. The change prevents users from attempting an unsupported operation that could lead to failed or unsafe transactions when using a Ledger/Trezor-like device. The issue was reported by zkao using a tool from zkSecurity, suggesting it was found during a security review, but the commit message does not explain the exact attack or failure scenario.
Receive: fix stale subaddress selection after switching accounts
subaddressListView.currentIndex was only reset when it equaled -1 (the initial sentinel), so switching to an account with fewer addresses left the Receive page showing the old index and its label while the QR/address itself already reflected the new account's primary address. onPageCompleted also hardcoded index 0 when setting current_address instead of using the selected index, so the shown address could disagree with the selected row's label even within the same account after revisiting the page.
Validate currentIndex against the current account's address count on page load, and share the address/label sync logic between the selection handler and onPageCompleted so both stay consistent.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validationprivacy or spend-authorization protocol
AI analysis · Low 25/100
This is a user-interface bug fix in the Monero wallet's Receive page. When a user switched between accounts, the page could show a label and QR code from one account while the displayed address belonged to another account, because the selected list row was not updated to match the new account. The fix makes sure the selected row and displayed address/label stay in sync. It is a consistency bug, not a cryptographic or network vulnerability.
53b5fa1 fix overlap in certain languages (SNeedlewoods)
ACKs: jpk68, selsta
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed 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 merge of pull request #4192 into the Monero GUI repository. The actual code change within that PR is a single, minor user-interface fix by contributor SNeedlewoods to prevent text overlap in certain languages. The rest of the diff is the initial population of the repository with the full Monero GUI source tree, build files, translations, images, and CI workflows. There is no security-relevant code change here.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is a routine code cleanup that swaps out old Qt programming interfaces for their newer replacements. It does not fix a security bug and does not introduce any obvious security weakness. The changes are purely about keeping the code compatible with newer versions of the Qt toolkit.
main: hide update popup during device passphrase prompt
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 18/100
This tiny change stops a software-update notification window from appearing while the user is entering their hardware wallet passphrase. The most likely real-world effect is avoiding a confusing or annoying overlap of two popups, not a serious security flaw. There is no direct evidence in the commit that this fixes an exploitable vulnerability.
seed or entropy pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 19/100
This is a large routine update that migrates the Monero GUI wallet's user-interface toolkit from Qt5 to Qt6. It touches build scripts, Docker images, QML interface files, and C++ source code. The change is primarily a dependency and framework upgrade, not a security patch. There is no direct evidence in the commit that it fixes or introduces a security vulnerability. The main security-relevant aspect is that moving to a newer, supported Qt branch removes exposure to unpatched Qt5 bugs over time, and the build now disables many unused Qt network and multimedia features, slightly shrinking the attack surface.
Security candidateDockerfiles: pin Qt to a commit hashby Thomas · 5564db67 · Jun 23, 2026 · 3 filesMessage 76 · AdequateModerate 66Details
Commit message · Thomas
Dockerfiles: pin Qt to a commit hash
Qt was cloned with -b ${QT_VERSION} --depth 1 but, unlike every other dependency in these files, never reset to a commit, so a moved upstream tag would silently change the Qt source built into the release.
Pin the qt5 superproject to its v5.15.19-lts-lgpl commit and let it resolve the submodules (git submodule update on linux/windows, init-repository on android), so only the qt5 hash is hardcoded. qt5 records the exact submodule commits, and the relative .gitmodules URLs keep the fetches on https.
Follow-up to #4613.
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access control
AI analysis · Moderate 66/100
This change tightens how the Monero GUI's build containers fetch the Qt user-interface library. Previously, the build scripts downloaded Qt using only a version tag (like 'v5.15.19-lts-lgpl'), which could silently point to different code if Qt's maintainers ever moved or re-created that tag. Now the scripts reset the downloaded Qt source to a specific, fixed commit hash, so every release build uses the exact same Qt code. This is a supply-chain hardening fix: it prevents a malicious or accidental tag change from slipping modified Qt code into Monero's official wallets.
Security candidateTransactionHistory: prevent CSV formula injection in writeCSVby Thomas · 0fbb1716 · Jun 18, 2026 · 1 fileMessage 73 · AdequateHigh 70Details
Commit message · Thomas
TransactionHistory: prevent CSV formula injection in writeCSV
writeCSV wrote the transaction note and subaddress label into the CSV stripping only the quote character. A cell beginning with =, +, - or @ can be interpreted as a formula by spreadsheet software on open, which CSV quoting does not prevent.
The transaction note can be attacker-controlled: a payment request's tx_description is stored as the note when the payment is sent, so a crafted note can run a spreadsheet formula when the user later exports and opens their history, potentially enabling data exfiltration or command execution.
Prefix affected fields with a single quote so they are treated as text; fields beginning with whitespace or a control character are prefixed too.
Co-authored-by: selsta <selsta@sent.at>
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
explicit security languageprivacy or spend-authorization protocolsigning or wallet path
AI analysis · High 70/100
This update fixes a security flaw in the Monero GUI wallet's export feature. When users exported their transaction history to a CSV file, the wallet stripped quote marks from transaction notes and address labels but did nothing else. If an attacker tricked a user into sending a payment with a specially crafted note beginning with =, +, -, or @, that note could become a spreadsheet formula. When the victim later exported and opened the CSV in Excel or similar software, the formula could run, potentially stealing data or running commands. The fix prefixes risky fields with a single quote so spreadsheets treat them as plain text.