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 fileWidely deployed RandomX CPU/GPU miner with pool and network-facing code.
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.
Sep 27 → Mar 3147 seen35 candidatesCompleteMar 31 → Jul 290 seen0 candidatesCompleteJul 29 → Aug 280 seen0 candidatesCompleteAug 28 → Sep 270 seen0 candidatesCompleteMessage quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
Public Git author strings; identities are not independently verified.
Last scanned 43 minutes ago
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 fileThis 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…
92705f2dby XMRig+10050−667286 filesThis 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 filesThis 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 fileThis 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 fileThis 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…
27d535d0by xmrig+1−11 fileThis 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 fileThis 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…
3b4e38baby xmrig+3−11 fileThis 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 …
8b33d249by SChernykh+3−11 fileThis 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…
a9356412by xmrig+16−124 filesThis 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 …
976a08efby SChernykh+16−124 filesThis 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…
17aa97e5by xmrig+12−42 filesThis 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…
48b29fd6by SChernykh+12−42 filesThis 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…
8464d474by xmrig+32−2714 filesThis 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…
26ee1cd2by SChernykh+32−2714 filesThis 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…
d9b39e8cby xmrig+116−486 filesThis 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 …
05dd6dccby SChernykh+116−486 filesThis 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…
316a3673by xmrig+49−156 filesThis 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…
42c943c0by SChernykh+49−156 filesThis 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…
c2c80807by xmrig+398−10310 filesExpand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
e41b28ef · Jan 15, 2026 · 3 filesInformational 12Improved RISC-V code
Why it was queuedThis commit refactors the RISC-V RandomX mining code in XMRig. It removes a dynamic analysis that tried to insert scratchpad prefetch instructions at an optimal point in each generated program, and instead always places the prefetch at a fixed, predictable location in the assembly template. The change is described by the author as an improvement/cleanup of RISC-V code. There is no indication in the commit or supplied references that this fixes a security vulnerability.
8ccf7de3 · Dec 31, 2025 · 10 filesInformational 15RISC-V: use vector hardware AES instead of scalar
Why it was queuedThis commit is a performance optimization for XMRig on RISC-V processors. It replaces a slower scalar (one-value-at-a-time) hardware AES implementation with a faster vector (multiple-values-at-once) AES implementation. There is no security vulnerability here; it is purely about making cryptocurrency mining faster on newer RISC-V CPUs.
d3a84c4b · Dec 29, 2025 · 6 filesInformational 15RISC-V: detect and use hardware AES
Why it was queuedThis commit adds support for RISC-V processors that have built-in AES hardware instructions. It is a performance optimization for the RandomX mining algorithm on RISC-V, not a security fix or vulnerability. There is no indication it introduces a security issue.
e1efd3dc · Dec 27, 2025 · 6 filesInformational 15RISC-V: auto-detect and use vector code for all RandomX AES functions
Why it was queuedThis commit is a performance optimization for XMRig on RISC-V processors. It adds new code paths that use RISC-V vector instructions (RVV) to speed up the AES-based hashing routines used by the RandomX mining algorithm. There is no indication this change fixes a security bug or introduces a known vulnerability; it is purely about making mining faster on RISC-V hardware.
f661e1eb · Dec 26, 2025 · 18 filesInformational 18RISC-V: vectorized RandomX main loop
Why it was queuedThis commit adds a new, faster RISC-V code path for the RandomX mining algorithm in XMRig. It is a performance optimization: it detects RISC-V vector (RVV) and optional bit-manipulation/prefetch extensions, then generates vectorized machine code for the main mining loop. There is no indication in the commit that it fixes a security bug or introduces a known vulnerability.
712a5a5e · Dec 23, 2025 · 1000 filesInformational 15Merge branch 'dev'
Why it was queuedThis is a routine merge of the 'dev' branch into the main XMRig cryptocurrency mining project. The commit adds the entire project source tree (about 319,000 lines across roughly 1,000 files) to the repository. There is no indication of a security patch, vulnerability fix, or malicious change in the supplied materials.
482a1f0b · Dec 11, 2025 · 8 filesInformational 21Linux: added support for transparent huge pages
Why it was queuedThis commit adds Linux-only support for 'transparent huge pages' in the XMRig cryptocurrency miner. Transparent huge pages are a normal Linux performance feature that can speed up memory-heavy mining work. The change only calls the standard Linux madvise() system call with MADV_HUGEPAGE when regular huge-page allocation fails, and does nothing on Windows. There is no direct security vulnerability visible in the diff, but enabling huge pages can sometimes make certain advanced memory-based side-channel attacks slightly easier in very specific scenarios. That is a general property of huge pages, not a flaw introduced by this commit.
23da1a90 · Dec 5, 2025 · 5 filesInformational 15RISC-V: added vectorized soft AES
Why it was queuedThis commit adds a new, faster software-based AES implementation for RISC-V processors that support the RISC-V vector extension. It is a performance optimization for the RandomX mining algorithm and does not appear to fix or introduce a security vulnerability.
7ef5142a · Nov 30, 2025 · 9 filesInformational 14RISC-V: added vectorized dataset init (activated by setting `init-avx2` to 1 in config.json)
Why it was queuedThis commit adds a new optional performance optimization for RandomX mining on RISC-V processors that support vector instructions. It introduces a vectorized way to initialize the RandomX dataset, controlled by a config setting called `init-avx2`. There is no indication in the commit that this fixes a security bug or introduces a vulnerability; it appears to be a normal performance feature for a specific CPU architecture.
e88009d5 · Nov 12, 2025 · 983 filesInformational 15add detection for MSVC/2026
Why it was queuedThis commit is a massive initial import or full repository snapshot of the XMRig cryptocurrency miner project, not a focused security patch. The title mentions adding detection for MSVC/2026, but the diff shows 983 files being added including the entire codebase, build system, documentation, third-party libraries, and a Windows kernel driver. There is no evidence of a security vulnerability being fixed or introduced in this commit itself.
5115597e · Nov 6, 2025 · 2 filesInformational 17Improved compatibility for automatically enabling huge pages on Linux systems without NUMA support.
Why it was queuedThis commit is a routine compatibility improvement for XMRig's huge-page memory setup on Linux. It makes the miner better at enabling large memory pages on systems that do not expose per-CPU-node (NUMA) huge-page statistics. There is no indication this change introduces a security vulnerability or fixes one; it simply broadens the paths the program reads from and writes to in the Linux /sys filesystem.
b02519b9 · Nov 4, 2025 · 6 filesInformational 15feat: initial support for haiku
Why it was queuedThis commit adds build and runtime support for the Haiku operating system to the XMRig cryptocurrency miner. It is a straightforward portability patch: it teaches the build system to recognize Haiku, adjusts compiler flags, adds Haiku to existing OS-specific code branches for byte swapping and thread affinity, and provides Haiku-specific memory allocation fallbacks. There is no indication of any security vulnerability being fixed or introduced.
27c8e609 · Oct 22, 2025 · 4 filesInformational 15Removed unused files
Why it was queuedThis commit simply deletes four RISC-V-related header files that the author says were unused. There is no change to active code, no bug fix, and no security patch. It is a routine cleanup that reduces the amount of code in the repository.
985fe06e · Oct 22, 2025 · 4 filesInformational 14RISC-V: test for instruction extensions
Why it was queuedThis commit adds a build-time check for optional RISC-V CPU instruction extensions (Zba and Zbb) in the XMRig cryptocurrency miner. It does not change how the program runs on existing machines; it only lets the compiler use faster instructions when building specifically for the machine doing the compilation. There is no security bug or vulnerability visible in the change.
75b63ddd · Oct 22, 2025 · 9 filesInformational 18RISC-V JIT compiler
Why it was queuedThis commit adds a new RISC-V 64-bit Just-In-Time (JIT) compiler for the RandomX mining algorithm in XMRig. It is a feature addition that brings RISC-V hardware up to parity with existing x86 and ARM64 JIT compilers. There is no indication in the commit message or diff that this is a security fix, backdoor, or vulnerability patch. The code follows the same pattern as the existing ARM64 JIT compiler and is authored by the same upstream RandomX contributor (tevador).
643b65f2 · Oct 22, 2025 · 30 filesInformational 19RISC-V Intergration
Why it was queuedThis commit adds support for RISC-V processors to the XMRig cryptocurrency miner. It is a large feature/porting patch that introduces new CPU detection, build-system logic, and SSE-to-RISC-V vector compatibility headers. There is no direct evidence in the commit that this is a security fix or that it introduces a deliberate vulnerability; it reads as an architecture-enablement change. However, the patch contains a number of low-quality or risky implementation choices—such as placeholder AES stubs, inline assembly that may not compile on all toolchains, hardcoded -march flags, and a performance guide that recommends -ffast-math and aggressive kernel tuning—that could lead to incorrect hashing results, build failures, or local system misconfiguration. These are reliability and correctness concerns rather than proven security flaws.
da5a5674 · Oct 15, 2025 · 2 filesInformational 15Added Zen4 (Hawk Point) CPUs detection
Why it was queuedThis commit simply adds detection for a new AMD Zen 4 CPU variant (Hawk Point, model 0x75 / 117) to XMRig's existing CPU identification logic. It mirrors an already-supported Zen 4 model and does not change security-sensitive behavior. There is no indication of a vulnerability or security fix.
a659397c · Oct 5, 2025 · 1 fileLow 32Fix: correct FCMP++ version number
Why it was queuedThis commit fixes a version-number check in the code that prepares Monero block templates. The software was incorrectly treating Monero protocol version 17 as if it were the older format, and only enabling the new FCMP++ output format at version 18. The patch lowers the threshold to version 17 so the correct output type is used. If left unfixed, miners using this code on Monero version 17 could produce blocks with the wrong output format, which would likely be rejected by the network and cause lost mining rewards rather than directly steal funds or corrupt the chain.
da683d8c · Oct 5, 2025 · 3 filesInformational 19Solo mining: added support for FCMP++ hardfork
Why it was queuedThis commit updates the XMRig mining software to recognize a new Monero block format that will be used after the upcoming FCMP++ network upgrade. It adds parsing support for two new pieces of data (a 'carrot view tag' and a 'janus anchor') and allows a new output type used by that upgrade. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine compatibility update so solo miners can continue working after the hardfork.