XM
← All projectsXMRig

XMRig

Widely deployed RandomX CPU/GPU miner with pool and network-facing code.

Mining softwareMoneroNormal
Repository coverage

58 commits in the local evidence base

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.

44security candidates9second-pass queue53AI analyses
0commits · 30 days
0commits · 60 days
0commits · 180 days
46commits · 365 days
Backfill bands
Sep 27 → Mar 3147 seen35 candidatesComplete
Mar 31 → Jul 290 seen0 candidatesComplete
Jul 29 → Aug 280 seen0 candidatesComplete
Aug 28 → Sep 270 seen0 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

44/100 average clarity
3Strong · 80–100
6Adequate · 60–79
30Thin · 40–59
19Opaque · 0–39
12security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
SChernykh272627041
xmrig1089061
XMRig12411021
rezky_nightky333093
Tony Wang111045
slayingripper111028
user0-07161111057
Willie Shen200048
HashVault100058
Analysis record

Published AI watches

Last scanned 47 minutes ago

Informational 15 AI analysisMessage 0 · Opaque
XM XMRigXMRig Mining softwareMonero

v6.26.0

This commit simply changes a version label from '6.26.0-dev' to '6.26.0' in a single header file. It is a routine release-versioning change with no functional code modifications and no security relevance.

b2ca7248by XMRig+1−11 file
No security note in commit
Informational 23 AI analysisMessage 28 · Opaque
XM XMRigXMRig Mining softwareMonero

Merge branch 'dev'

This is a large routine feature release for the XMRig cryptocurrency miner. The main changes add support for a new mining algorithm variant called RandomX v2 (used by an upcoming Monero network upgrade), improve performance on RISC-V and Z…

New RandomX v2 algorithm support with share commitment fieldFCMP++ block template parsing changes (Merkle tree path/branch handling)Keepalive timer logic fix
92705f2dby XMRig+10050−667286 files
No security note in commit
Informational 15 AI analysisMessage 0 · Opaque
XM XMRigXMRig Mining softwareMonero

v6.26.0-dev

This commit is a routine version bump for the next development release of XMRig, a cryptocurrency mining program. It only updates the version number and copyright year, and adds a changelog listing new features and bug fixes from previous …

4f58a7afby XMRig+20−62 files
No security note in commit
Informational 19 AI analysisMessage 53 · Thin
XM XMRigXMRig Mining softwareMonero

Merge pull request #3790 from SChernykh/dev

This is a tiny one-line build fix for ARM64 processors. It changes a memory prefetch helper to accept a read-only (const) pointer, which allows the code to compile on ARM64 systems. There is no security issue visible in the change itself.

806cfc3fby xmrig+1−11 file
No security note in commit
Informational 19 AI analysisMessage 45 · Thin
XM XMRigXMRig Mining softwareMonero

Fix arm64 builds (attempt number 2)

This is a one-line build fix for ARM64 processors. It changes a memory prefetch helper to accept read-only (const) pointers, which is required by newer or stricter ARM64 compilers. There is no security bug being fixed here—just a compilati…

84352c71by SChernykh+1−11 file
No security note in commit
Informational 18 AI analysisMessage 53 · Thin
XM XMRigXMRig Mining softwareMonero

Merge pull request #3789 from SChernykh/dev

This is a minor build-compatibility fix for XMRig when compiled with the Clang compiler on 64-bit ARM (ARM64) processors. It changes a preprocessor condition so that Clang on ARM64 does not try to use a compiler feature (__builtin_prefetch…

No security-relevant signals detected in the diff or commit metadata.Change is confined to a preprocessor guard controlling prefetch macros.No pointer arithmetic, allocation, input parsing, authentication, or cryptographic changes.
27d535d0by xmrig+1−11 file
No security note in commit
Informational 19 AI analysisMessage 28 · Opaque
XM XMRigXMRig Mining softwareMonero

Fixed clang arm64 builds

This is a one-line build fix for compiling XMRig on ARM64 systems using the Clang compiler. It changes a preprocessor condition so that Clang on ARM64 does not try to use a GCC-specific memory prefetch instruction that Clang does not suppo…

9d296c7fby SChernykh+1−11 file
No security note in commit
Informational 22 AI analysisMessage 68 · Adequate
XM XMRigXMRig Mining softwareMonero

Merge pull request #3785 from SChernykh/dev

This patch changes how XMRig resets its internal counter (nonce) when switching between the user's mining job and the built-in donation mining job. Previously, the nonce was reset during these switches, which could cause duplicate work and…

No direct security signals in diffChange relates to mining correctness/efficiency, not access control or memory safetyIssue reference (#3669) suggests bug fix for stale/duplicate shares, not a security flaw
3b4e38baby xmrig+3−11 file
No security note in commit
Informational 19 AI analysisMessage 58 · Thin
XM XMRigXMRig Mining softwareMonero

Don't reset nonce during donation rounds (possible fix for #3669)

This is a small bug-fix change in the XMRig cryptocurrency mining software. It changes how the mining 'nonce' (a kind of counter) is reset when the miner briefly switches to a 'donation round' (a short period where mined rewards go to the …

No security keywords in commit title or messageNo CVE, advisory, or security-fix language presentChange relates to mining job/nonce handling, not input validation, authentication, or cryptography
8b33d249by SChernykh+3−11 file
No security note in commit
Informational 18 AI analysisMessage 68 · Adequate
XM XMRigXMRig Mining softwareMonero

Merge pull request #3783 from SChernykh/dev

This commit fixes how XMRig's RandomX mining code preloads data from the RandomX dataset before starting the main hashing loop. The old prefetch was only done inside assembly prologue code and only used one address, which was wrong for the…

No security-relevant signals detected in diff or commit metadataChange is a correctness/performance fix for RandomX dataset prefetchingNo input validation, memory allocation, cryptographic boundary, or privilege changes
a9356412by xmrig+16−124 files
No security note in commit
Informational 19 AI analysisMessage 45 · Thin
XM XMRigXMRig Mining softwareMonero

Fixed initial dataset prefetch for RandomX v2

This commit moves where a data prefetch happens in the RandomX cryptocurrency mining code and adds support for a second prefetch in a newer RandomX variant. Prefetch instructions only hint to the CPU what memory might be needed soon; they …

No security-relevant signals detected in the diff.Prefetch instructions are non-binding performance hints and cannot be used to corrupt memory or leak secrets directly.The moved prefetch uses the same mask-and-add computation as the removed assembly prefetch, with no change to the effective address calculation.
976a08efby SChernykh+16−124 files
No security note in commit
Low 26 AI analysisMessage 68 · Adequate
XM XMRigXMRig Mining softwareMonero

Merge pull request #3782 from SChernykh/dev

This commit changes how the XMRig miner handles a new RandomX variant (RandomX v2). Previously, when switching to or from RandomX v2, the miner would regenerate its large dataset. Now it reuses the existing dataset, treating RandomX v2 and…

Algorithm family equivalence logic changeDataset initialization path modifiedNo input validation changes
17aa97e5by xmrig+12−42 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
XM XMRigXMRig Mining softwareMonero

RandomX v2: don't update dataset when switching to/from it

This commit tweaks how the XMRig miner handles switching between two closely related RandomX algorithm variants (RX/0 and RX/V2). It avoids rebuilding the large RandomX dataset when the miner switches between these two variants, because th…

Algorithm-variant equivalence logic introduced in seed comparisonDataset readiness check reordered relative to algorithm switchNo input sanitization, bounds checking, or cryptographic changes present
48b29fd6by SChernykh+12−42 files
No security note in commit
Informational 17 AI analysisMessage 53 · Thin
XM XMRigXMRig Mining softwareMonero

Merge pull request #3778 from SChernykh/dev

This commit is titled 'ARM64 fixes' and changes how the RandomX mining algorithm's ARM64 code handles AES lookup tables and memory checks. The code now stores AES encryption/decryption table addresses into a dynamically allocated code buff…

Runtime pointer patching into executable JIT code bufferRemoval of large static AES lookup tables from assemblyAddition of free-memory guard before large memory allocation for NUMA mining
8464d474by xmrig+32−2714 files
No security note in commit
Low 27 AI analysisMessage 21 · Opaque
XM XMRigXMRig Mining softwareMonero

ARM64 fixes

This commit fixes two ARM64-specific issues in the XMRig cryptocurrency miner. First, it removes duplicate copies of AES lookup tables from the compiled RandomX code, instead reusing the existing tables already in memory. Second, it adds a…

Executable code is patched with runtime pointers to AES lookup tables (self-modifying code / W^X interaction)Memory availability is now validated before enabling multi-node NUMA allocation, preventing potential overallocationRemoval of duplicated AES tables reduces code/data size and eliminates a potential source of inconsistency
26ee1cd2by SChernykh+32−2714 files
No security note in commit
Informational 12 AI analysisMessage 53 · Thin
XM XMRigXMRig Mining softwareMonero

Merge pull request #3776 from SChernykh/dev

This commit updates XMRig's mining code to support a new Monero block format called FCMP++ (a recent network upgrade). It changes how the software builds the 'Merkle tree' cryptographic proof that links the coinbase transaction to the bloc…

No security-relevant keywords in commit title or messageChanges are protocol compatibility additions for Monero FCMP++ upgradeMerkle tree path handling is corrected for new block layout
d9b39e8cby xmrig+116−486 files
No security note in commit
Informational 22 AI analysisMessage 45 · Thin
XM XMRigXMRig Mining softwareMonero

Sync changes with xmrig-proxy

This commit updates XMRig's mining code to support a new Monero block format called FCMP++. It changes how the software builds the transaction hash tree (Merkle tree) used when mining. There is no clear security bug here; it appears to be …

Merkle tree path handling added, which if incorrect could cause invalid block hashingFCMP++ block template parsing changes how transaction hashes are indexedNo explicit bounds checks visible in the rewritten Merkle loop, though sizes are derived from count
05dd6dccby SChernykh+116−486 files
No security note in commit
Informational 19 AI analysisMessage 68 · Adequate
XM XMRigXMRig Mining softwareMonero

Merge pull request #3775 from SChernykh/dev

This commit updates the XMRig mining software to support a new RandomX v2 protocol feature. When a mining pool asks for it, the miner now includes an extra 'commitment' value alongside its share submissions. The change is a feature additio…

Protocol feature addition (RandomX v2 commitment field)Buffer size increase in stratum client (256 -> 320 bytes)Shared extra_data buffer used for two different-sized data types (32-byte commitment vs 64-byte signature)
316a3673by xmrig+49−156 files
No security note in commit
Informational 19 AI analysisMessage 50 · Thin
XM XMRigXMRig Mining softwareMonero

RandomX v2: added `commitment` field to stratum submit message

This commit updates the XMRig mining software to support a new 'commitment' field required by an upcoming RandomX version 2 protocol. It changes how miners package and submit proof-of-work results to mining pools. There is no direct eviden…

Protocol field addition for RandomX v2 stratum submit messageBuffer size increase in stratum client temporary buffer (256 -> 320 bytes)JIT compiler alignment threshold change for CFROUND branches
42c943c0by SChernykh+49−156 files
No security note in commit
Informational 18 AI analysisMessage 53 · Thin
XM XMRigXMRig Mining softwareMonero

Merge pull request #3774 from SChernykh/dev

This commit adds support for a new version of the RandomX mining algorithm (RandomX v2) on RISC-V processors. It is a feature/algorithm update, not a security patch. There is no indication in the commit that it fixes a vulnerability or tha…

No security-relevant language in commit title or messageNo CVE, advisory, or bug report references presentChanges are confined to RISC-V RandomX mining algorithm implementation
c2c80807by xmrig+398−10310 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateMerge branch 'dev'by XMRig · 92705f2d · Mar 28, 2026 · 86 filesMessage 28 · OpaqueInformational 23Details
Commit message · XMRig

Merge branch 'dev'

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 23/100

This is a large routine feature release for the XMRig cryptocurrency miner. The main changes add support for a new mining algorithm variant called RandomX v2 (used by an upcoming Monero network upgrade), improve performance on RISC-V and Zen5 processors, fix a few minor bugs, and update documentation. There is no clear security vulnerability being patched; it is primarily a functionality and performance update.

Security candidateMerge pull request #3790 from SChernykh/devby xmrig · 806cfc3f · Mar 3, 2026 · 1 fileMessage 53 · ThinInformational 19Details
Commit message · xmrig

Merge pull request #3790 from SChernykh/dev

Fix arm64 builds (attempt number 2)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This is a tiny one-line build fix for ARM64 processors. It changes a memory prefetch helper to accept a read-only (const) pointer, which allows the code to compile on ARM64 systems. There is no security issue visible in the change itself.

Security candidateFix arm64 builds (attempt number 2)by SChernykh · 84352c71 · Mar 3, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · SChernykh

Fix arm64 builds (attempt number 2)

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy path
AI analysis · Informational 19/100

This is a one-line build fix for ARM64 processors. It changes a memory prefetch helper to accept read-only (const) pointers, which is required by newer or stricter ARM64 compilers. There is no security bug being fixed here—just a compilation error being resolved.

Security candidateMerge pull request #3789 from SChernykh/devby xmrig · 27d535d0 · Mar 3, 2026 · 1 fileMessage 53 · ThinInformational 18Details
Commit message · xmrig

Merge pull request #3789 from SChernykh/dev

Fixed clang arm64 builds

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 18/100

This is a minor build-compatibility fix for XMRig when compiled with the Clang compiler on 64-bit ARM (ARM64) processors. It changes a preprocessor condition so that Clang on ARM64 does not try to use a compiler feature (__builtin_prefetch) that may not be available, which could otherwise cause the build to fail. There is no indication this change fixes a security vulnerability or affects runtime behavior on already-working builds.

Security candidateFixed clang arm64 buildsby SChernykh · 9d296c7f · Mar 3, 2026 · 1 fileMessage 28 · OpaqueInformational 19Details
Commit message · SChernykh

Fixed clang arm64 builds

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy path
AI analysis · Informational 19/100

This is a one-line build fix for compiling XMRig on ARM64 systems using the Clang compiler. It changes a preprocessor condition so that Clang on ARM64 does not try to use a GCC-specific memory prefetch instruction that Clang does not support in that configuration. There is no indication this affects runtime security, user data, or mining behavior; it only affects whether the source code compiles successfully.

Security candidateMerge pull request #3783 from SChernykh/devby xmrig · a9356412 · Feb 15, 2026 · 4 filesMessage 68 · AdequateInformational 18Details
Commit message · xmrig

Merge pull request #3783 from SChernykh/dev

Fixed initial dataset prefetch for RandomX v2

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 18/100

This commit fixes how XMRig's RandomX mining code preloads data from the RandomX dataset before starting the main hashing loop. The old prefetch was only done inside assembly prologue code and only used one address, which was wrong for the newer RandomX v2 algorithm that needs two separate prefetches. The fix moves the prefetch logic into the portable C++ virtual machine code and adds a second prefetch when RandomX v2 is active. It also enables actual non-temporal prefetch instructions for GCC builds, whereas before they were no-ops. This is a correctness/performance bug in mining output, not a security vulnerability.

Security candidateFixed initial dataset prefetch for RandomX v2by SChernykh · 976a08ef · Feb 15, 2026 · 4 filesMessage 45 · ThinInformational 19Details
Commit message · SChernykh

Fixed initial dataset prefetch for RandomX v2

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 19/100

This commit moves where a data prefetch happens in the RandomX cryptocurrency mining code and adds support for a second prefetch in a newer RandomX variant. Prefetch instructions only hint to the CPU what memory might be needed soon; they do not change program results and cannot be used to attack the program. The change appears to be a performance/correctness fix for mining behavior, not a security patch.

Security candidateMerge pull request #3782 from SChernykh/devby xmrig · 17aa97e5 · Feb 15, 2026 · 2 filesMessage 68 · AdequateLow 26Details
Commit message · xmrig

Merge pull request #3782 from SChernykh/dev

RandomX v2: don't update dataset when switching to/from it

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Low 26/100

This commit changes how the XMRig miner handles a new RandomX variant (RandomX v2). Previously, when switching to or from RandomX v2, the miner would regenerate its large dataset. Now it reuses the existing dataset, treating RandomX v2 and the original RandomX as having the same 'seed algorithm.' This is a performance/correctness optimization for a new algorithm variant, not a fix for an exploitable security vulnerability.

Security candidateRandomX v2: don't update dataset when switching to/from itby SChernykh · 48b29fd6 · Feb 13, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · SChernykh

RandomX v2: don't update dataset when switching to/from it

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 15/100

This commit tweaks how the XMRig miner handles switching between two closely related RandomX algorithm variants (RX/0 and RX/V2). It avoids rebuilding the large RandomX dataset when the miner switches between these two variants, because they can share the same dataset. The change is a performance/correctness optimization for mining operations, not a fix for an externally exploitable security vulnerability.

Security candidateMerge pull request #3778 from SChernykh/devby xmrig · 8464d474 · Feb 4, 2026 · 4 filesMessage 53 · ThinInformational 17Details
Commit message · xmrig

Merge pull request #3778 from SChernykh/dev

ARM64 fixes

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 17/100

This commit is titled 'ARM64 fixes' and changes how the RandomX mining algorithm's ARM64 code handles AES lookup tables and memory checks. The code now stores AES encryption/decryption table addresses into a dynamically allocated code buffer at runtime, and adds a free-memory check before enabling multi-NUMA mining. There is no direct evidence in the commit message or diff that this is a security fix, and the changes appear to be correctness or performance-related for ARM64 mining. The memory check is a defensive hardening measure, not a fix for an exploitable vulnerability.

Security candidateARM64 fixesby SChernykh · 26ee1cd2 · Feb 3, 2026 · 4 filesMessage 21 · OpaqueLow 27Details
Commit message · SChernykh

ARM64 fixes

- Added a check for free memory before enabling NUMA
- Removed duplicate AES tables from the ARM64 JIT compiler

Fixes #3729 and #3777

21/100 · OpaqueMessage clarity
✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference! Very short subject! Too few words to establish purpose! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy path
AI analysis · Low 27/100

This commit fixes two ARM64-specific issues in the XMRig cryptocurrency miner. First, it removes duplicate copies of AES lookup tables from the compiled RandomX code, instead reusing the existing tables already in memory. Second, it adds a memory check before enabling NUMA (multi-socket memory) mode to avoid requesting more memory than the system has free. These are correctness and stability fixes rather than obvious security vulnerabilities, though the AES table pointer patching involves writing memory addresses into executable code.

Security candidateMerge pull request #3776 from SChernykh/devby xmrig · d9b39e8c · Feb 2, 2026 · 6 filesMessage 53 · ThinInformational 12Details
Commit message · xmrig

Merge pull request #3776 from SChernykh/dev

Sync changes with xmrig-proxy

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 12/100

This commit updates XMRig's mining code to support a new Monero block format called FCMP++ (a recent network upgrade). It changes how the software builds the 'Merkle tree' cryptographic proof that links the coinbase transaction to the block header. There is no indication in the commit or supplied references that this fixes a security vulnerability; it appears to be a compatibility/feature update to keep the miner working with the latest Monero protocol.

Security candidateSync changes with xmrig-proxyby SChernykh · 05dd6dcc · Feb 2, 2026 · 6 filesMessage 45 · ThinInformational 22Details
Commit message · SChernykh

Sync changes with xmrig-proxy

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 · Informational 22/100

This commit updates XMRig's mining code to support a new Monero block format called FCMP++. It changes how the software builds the transaction hash tree (Merkle tree) used when mining. There is no clear security bug here; it appears to be a feature update to keep the miner compatible with upcoming Monero network changes. However, the commit message is vague and the changes are complex, so a full security review would need more context.

Security candidateMerge pull request #3775 from SChernykh/devby xmrig · 316a3673 · Feb 1, 2026 · 6 filesMessage 68 · AdequateInformational 19Details
Commit message · xmrig

Merge pull request #3775 from SChernykh/dev

RandomX v2: added `commitment` field to stratum submit message

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit updates the XMRig mining software to support a new RandomX v2 protocol feature. When a mining pool asks for it, the miner now includes an extra 'commitment' value alongside its share submissions. The change is a feature addition for cryptocurrency mining protocol compatibility, not a fix for a security vulnerability in the traditional sense. There is also a small adjustment to how generated code is aligned for a CPU performance tweak.

Security candidateRandomX v2: added `commitment` field to stratum submit messageby SChernykh · 42c943c0 · Feb 1, 2026 · 6 filesMessage 50 · ThinInformational 19Details
Commit message · SChernykh

RandomX v2: added `commitment` field to stratum submit message

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 19/100

This commit updates the XMRig mining software to support a new 'commitment' field required by an upcoming RandomX version 2 protocol. It changes how miners package and submit proof-of-work results to mining pools. There is no direct evidence this is a security fix for an exploitable vulnerability; it appears to be a protocol compatibility update. A small adjustment to CPU jump alignment in the RandomX JIT compiler is also included, likely to preserve correct behavior on newer CPU features, but the diff alone does not show a security bug.

Security candidateMerge pull request #3774 from SChernykh/devby xmrig · c2c80807 · Feb 1, 2026 · 10 filesMessage 53 · ThinInformational 18Details
Commit message · xmrig

Merge pull request #3774 from SChernykh/dev

RandomX v2 (RISC-V)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 18/100

This commit adds support for a new version of the RandomX mining algorithm (RandomX v2) on RISC-V processors. It is a feature/algorithm update, not a security patch. There is no indication in the commit that it fixes a vulnerability or that the project treats it as a security-relevant change.

Security candidateRandomX v2 (RISC-V)by SChernykh · d82d7f3f · Jan 31, 2026 · 10 filesMessage 28 · OpaqueInformational 16Details
Commit message · SChernykh

RandomX v2 (RISC-V)

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 16/100

This commit adds and updates RISC-V (a CPU architecture) support for the RandomX mining algorithm in XMRig. It introduces new code paths for a 'RandomX v2' variant, including optional software-based AES and tweaks to how data is prefetched and rounded. There is no indication in the commit or title that this fixes a security vulnerability; it reads as a performance and compatibility update for RISC-V miners.

Security candidateRandomX v2 (ARM64)by SChernykh · cb600194 · Jan 31, 2026 · 4 filesMessage 28 · OpaqueInformational 15Details
Commit message · SChernykh

RandomX v2 (ARM64)

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 15/100

This commit updates the RandomX mining algorithm implementation for 64-bit ARM (ARM64/AArch64) processors. It adds support for a new variant of RandomX (v2), including AES-based mixing of register groups, a software fallback for devices without hardware AES, and a tweak to floating-point rounding behavior. These are normal, expected changes for a cryptocurrency miner to stay compatible with an evolving proof-of-work algorithm. There is no indication in the commit or supplied references that this is a security fix or vulnerability.

Security candidateRandomX v2 + commitmentsby SChernykh · 9d71358f · Jan 30, 2026 · 26 filesMessage 28 · OpaqueInformational 15Details
Commit message · SChernykh

RandomX v2 + commitments

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 15/100

This commit adds support for a new mining algorithm variant called 'RandomX v2' plus a 'commitments' feature in the XMRig cryptocurrency miner. It is a routine protocol/algorithm update: new benchmark hashes, new algorithm identifiers, new assembly and JIT compiler code paths, and a small change to how CPU workers compute and store an extra commitment value when the new variant is active. There is no indication of a security vulnerability, backdoor, or malicious behavior in the diff.

Security candidatefix: cross typos detail below:by rezky_nightky · 67cc6cfd · Jan 21, 2026 · 15 filesMessage 90 · StrongInformational 15Details
Commit message · rezky_nightky

fix: cross typos detail below:

What I did
Repository rules / exclusions
I didn’t find repo-specific spelling tooling already in place (no existing codespell config).
Given this is a C/C++ repo with vendored sources, I treated src/3rdparty/** as third-party and excluded it from typo fixing (and encoded that in the new .codespellrc).
Typos fixed (first-party only)
Docs
CHANGELOG.md: perfomance -> performance
doc/API.md: optionaly -> optionally, Offical -> Official
doc/BENCHMARK.md: parameteres -> parameters
doc/CPU.md: loosing -> losing, instuctions -> instructions
doc/CHANGELOG_OLD.md: multiple obvious text typos like Breaked -> Broken, singal -> signal, previos -> previous, secons -> seconds, automaticaly -> automatically, perfomance -> performance
Code comments / doc comments (safe text-only changes)
src/base/crypto/sha3.cpp: Inteface -> Interface (comment banner)
src/backend/opencl/cl/cn/cryptonight.cl: performe -> perform, crashs -> crashes (comments)
src/backend/opencl/cl/kawpow/kawpow.cl: regsters -> registers, intial -> initial (comments)
src/crypto/randomx/aes_hash.cpp: intial -> initial (comment)
src/crypto/randomx/intrin_portable.h: cant -> can't (comment)
src/crypto/randomx/randomx.h: intialization -> initialization (doc comment)
src/crypto/cn/c_jh.c: intital -> initial (comment)
src/crypto/cn/skein_port.h: varaiable -> variable (comment)
src/backend/opencl/cl/cn/wolf-skein.cl: Build-in -> Built-in (comment)
What I intentionally did NOT change
Anything under src/3rdparty/** (vendored).
A few remaining codespell hits are either:
Upstream/embedded sources we excluded (groestl256.cl, jh.cl contain Projet)
Potentially valid identifier/name (Carmel CPU codename)
Low-risk token in codegen comments (vor inside an instruction comment)
These are handled via ignore rules in .codespellrc instead of modifying code.

Added: .codespellrc
Created /.codespellrc with:

skip entries for vendored / embedded upstream areas:
./src/3rdparty
./src/crypto/ghostrider
./src/crypto/randomx/blake2
./src/crypto/cn/sse2neon.h
./src/backend/opencl/cl/cn/groestl256.cl
./src/backend/opencl/cl/cn/jh.cl
ignore-words-list for:
Carmel
vor
Verification
codespell . --config ./.codespellrc now exits clean (exit code 0).

Signed-off-by: rezky_nightky <with.rezky@gmail.com>

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationproof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 15/100

This commit only fixes spelling mistakes in documentation and code comments. No program logic, configuration handling, or executable code was changed, so it cannot affect security or functionality.

Security candidateRevert "Merge branch 'pr3764' into dev"by XMRig · db24bf51 · Jan 21, 2026 · 22 filesMessage 68 · AdequateInformational 12Details
Commit message · XMRig

Revert "Merge branch 'pr3764' into dev"

This reverts commit 0d9a372e494bd602d7eb40704c91ca7e6dc47f76, reversing
changes made to 1a04bf2904b8cb29320f577c78ad88f097c253a7.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathseed or entropy path
AI analysis · Informational 12/100

This commit is a wholesale revert of a previous merge (pr3764). It undoes a large set of changes across documentation, comments, and several source files. The reverted code appears to have been a mix of typo corrections, minor cleanups, and some functional changes to latency tracking, job-result handling, thread cleanup, and memory management. Because the commit removes those changes rather than introducing new behavior, it does not by itself create a security vulnerability. It may restore older, potentially less safe patterns (for example, calling thread join without checking joinability, or removing safeguards in the job-results queue), but the commit message gives no security rationale and there is no direct evidence of an exploitable flaw being introduced here.

Security candidatefeat: stability improvements, see detail belowby rezky_nightky · 5ca48282 · Jan 21, 2026 · 7 filesMessage 100 · StrongModerate 53Details
Commit message · rezky_nightky

feat: stability improvements, see detail below

Key stability improvements made (deterministic + bounded)
1) Bounded memory usage in long-running stats
Fixed unbounded growth in NetworkState latency tracking:
Replaced std::vector<uint16_t> m_latency + push_back() with a fixed-size ring buffer (kLatencyWindow = 1024) and explicit counters.
Median latency computation now operates on at most 1024 samples, preventing memory growth and avoiding performance cliffs from ever-growing copies/sorts.
2) Prevent crash/UAF on shutdown + more predictable teardown
Controller shutdown ordering (Controller::stop()):
Now stops m_miner before destroying m_network.
This reduces chances of worker threads submitting results into a network listener that’s already destroyed.
Thread teardown hardening (backend/common/Thread.h):
Destructor now checks std::thread::joinable() before join().
Avoids std::terminate() if a thread object exists but never started due to early exit/error paths.
3) Fixed real leaks (including executable memory)
Executable memory leak fixed (crypto/cn/CnCtx.cpp):
CnCtx::create() allocates executable memory for generated_code via VirtualMemory::allocateExecutableMemory(0x4000, ...).
Previously CnCtx::release() only _mm_free()’d the struct, leaking the executable mapping.
Now CnCtx::release() frees generated_code before freeing the ctx.
GPU verification leak fixed (net/JobResults.cpp):
In getResults() (GPU result verification), a cryptonight_ctx was created via CnCtx::create() but never released.
Added CnCtx::release(ctx, 1).
4) JobResults: bounded queues + backpressure + safe shutdown semantics
The old JobResults could:

enqueue unlimited std::list items (m_results, m_bundles) → unbounded RAM,
call uv_queue_work per async batch → unbounded libuv threadpool backlog,
delete handler directly while worker threads might still submit → potential crash/UAF.
Changes made:

Hard queue limits:
kMaxQueuedResults = 4096
kMaxQueuedBundles = 256
Excess is dropped (bounded behavior under load).
Async coalescing:
Only one pending async notification at a time (m_pendingAsync), reducing eventfd/uv wake storms.
Bounded libuv work scheduling:
Only one uv_queue_work is scheduled at a time (m_workScheduled), preventing CPU starvation and unpredictable backlog.
Safe shutdown:
JobResults::stop() now detaches global handler first, then calls handler->stop().
Shutdown detaches m_listener, clears queues, and defers deletion until in-flight work is done.
Defensive bound on GPU result count:
Clamp count to 0xFF inside JobResults as well, not just in the caller, to guard against corrupted kernels/drivers.
5) Idempotent cleanup
VirtualMemory::destroy() now sets pool = nullptr after delete:
prevents accidental double-delete on repeated teardown paths.
Verification performed
codespell . --config ./.codespellrc: clean
CMake configure + build completed successfully (Release build)

Signed-off-by: rezky_nightky <with.rezky@gmail.com>

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Moderate 53/100

This commit is a hardening patch for the XMRig cryptocurrency miner. It fixes several stability problems that could also have security consequences: unbounded memory growth in network statistics, a shutdown crash where worker threads could use an already-destroyed network object, a leak of executable memory used by mining code, a leaked cryptography context during GPU result checking, and unsafe unbounded queues in the job-results processor. The patch adds size limits, safer teardown ordering, and proper cleanup of executable memory and contexts. There is no claim in the commit that these issues are exploitable for code execution or were reported as security vulnerabilities.

Security candidatefix: cross typos detail below:by rezky_nightky · cb751150 · Jan 21, 2026 · 15 filesMessage 90 · StrongInformational 15Details
Commit message · rezky_nightky

fix: cross typos detail below:

What I did
Repository rules / exclusions
I didn’t find repo-specific spelling tooling already in place (no existing codespell config).
Given this is a C/C++ repo with vendored sources, I treated src/3rdparty/** as third-party and excluded it from typo fixing (and encoded that in the new .codespellrc).
Typos fixed (first-party only)
Docs
CHANGELOG.md: perfomance -> performance
doc/API.md: optionaly -> optionally, Offical -> Official
doc/BENCHMARK.md: parameteres -> parameters
doc/CPU.md: loosing -> losing, instuctions -> instructions
doc/CHANGELOG_OLD.md: multiple obvious text typos like Breaked -> Broken, singal -> signal, previos -> previous, secons -> seconds, automaticaly -> automatically, perfomance -> performance
Code comments / doc comments (safe text-only changes)
src/base/crypto/sha3.cpp: Inteface -> Interface (comment banner)
src/backend/opencl/cl/cn/cryptonight.cl: performe -> perform, crashs -> crashes (comments)
src/backend/opencl/cl/kawpow/kawpow.cl: regsters -> registers, intial -> initial (comments)
src/crypto/randomx/aes_hash.cpp: intial -> initial (comment)
src/crypto/randomx/intrin_portable.h: cant -> can't (comment)
src/crypto/randomx/randomx.h: intialization -> initialization (doc comment)
src/crypto/cn/c_jh.c: intital -> initial (comment)
src/crypto/cn/skein_port.h: varaiable -> variable (comment)
src/backend/opencl/cl/cn/wolf-skein.cl: Build-in -> Built-in (comment)
What I intentionally did NOT change
Anything under src/3rdparty/** (vendored).
A few remaining codespell hits are either:
Upstream/embedded sources we excluded (groestl256.cl, jh.cl contain Projet)
Potentially valid identifier/name (Carmel CPU codename)
Low-risk token in codegen comments (vor inside an instruction comment)
These are handled via ignore rules in .codespellrc instead of modifying code.

Added: .codespellrc
Created /.codespellrc with:

skip entries for vendored / embedded upstream areas:
./src/3rdparty
./src/crypto/ghostrider
./src/crypto/randomx/blake2
./src/crypto/cn/sse2neon.h
./src/backend/opencl/cl/cn/groestl256.cl
./src/backend/opencl/cl/cn/jh.cl
ignore-words-list for:
Carmel
vor
Verification
codespell . --config ./.codespellrc now exits clean (exit code 0).

Signed-off-by: rezky_nightky <with.rezky@gmail.com>

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationproof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 15/100

This commit is a spelling and typo cleanup. It fixes misspelled words in documentation files and code comments, and adds a configuration file for an automated spell-checker. No program logic, configuration parsing, network handling, or cryptographic calculations were changed. There is no security impact.

Security candidateOptimized VAES codeby SChernykh · 45d0a15c · Jan 16, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · SChernykh

Optimized VAES code

Use only 1 mask instead of 2

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy path
AI analysis · Informational 15/100

This is a small performance cleanup in a cryptocurrency mining algorithm's AES encryption helper. It replaces two different bit masks with a single shared mask and swaps the argument order where needed so the result stays the same. There is no security bug being fixed here.

Security candidateRandomX: added VAES-512 support for Zen5by SChernykh · ed80a8a8 · Jan 16, 2026 · 3 filesMessage 45 · ThinInformational 18Details
Commit message · SChernykh

RandomX: added VAES-512 support for Zen5

+0.1-0.2% hashrate improvement.

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
proof-of-work or emission validationcryptography-sensitive pathseed or entropy path
AI analysis · Informational 18/100

This commit adds a new performance-optimized code path for AMD Zen 5 processors in the RandomX cryptocurrency-mining algorithm. It uses wider AVX-512 AES instructions to slightly increase mining speed. There is no indication this change fixes a security bug or introduces a known vulnerability; it is a routine optimization.