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 43 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 candidateImproved RISC-V codeby SChernykh · e41b28ef · Jan 15, 2026 · 3 filesMessage 28 · OpaqueInformational 12Details
Commit message · SChernykh

Improved RISC-V code

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 12/100

This 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.

Security candidateRISC-V: use vector hardware AES instead of scalarby SChernykh · 8ccf7de3 · Dec 31, 2025 · 10 filesMessage 45 · ThinInformational 15Details
Commit message · SChernykh

RISC-V: use vector hardware AES instead of scalar

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 15/100

This 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.

Security candidateRISC-V: detect and use hardware AESby SChernykh · d3a84c4b · Dec 29, 2025 · 6 filesMessage 45 · ThinInformational 15Details
Commit message · SChernykh

RISC-V: detect and use hardware AES

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 15/100

This 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.

Security candidateRISC-V: auto-detect and use vector code for all RandomX AES functionsby SChernykh · e1efd3dc · Dec 27, 2025 · 6 filesMessage 50 · ThinInformational 15Details
Commit message · SChernykh

RISC-V: auto-detect and use vector code for all RandomX AES functions

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 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.

Security candidateRISC-V: vectorized RandomX main loopby SChernykh · f661e1eb · Dec 26, 2025 · 18 filesMessage 45 · ThinInformational 18Details
Commit message · SChernykh

RISC-V: vectorized RandomX main loop

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, 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.

Security candidateMerge branch 'dev'by XMRig · 712a5a5e · Dec 23, 2025 · 1000 filesMessage 28 · OpaqueInformational 15Details
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 pathsigning or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This 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.

Security candidateLinux: added support for transparent huge pagesby SChernykh · 482a1f0b · Dec 11, 2025 · 8 filesMessage 45 · ThinInformational 21Details
Commit message · SChernykh

Linux: added support for transparent huge pages

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 21/100

This 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.

Security candidateRISC-V: added vectorized soft AESby SChernykh · 23da1a90 · Dec 5, 2025 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · SChernykh

RISC-V: added vectorized soft AES

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 15/100

This 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.

Security candidateRISC-V: added vectorized dataset init (activated by setting `init-avx2` to 1 in config.json)by SChernykh · 7ef5142a · Nov 30, 2025 · 9 filesMessage 50 · ThinInformational 14Details
Commit message · SChernykh

RISC-V: added vectorized dataset init (activated by setting `init-avx2` to 1 in config.json)

50/100 · ThinMessage clarity
✓ Specific, 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 14/100

This 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.

Security candidateadd detection for MSVC/2026by Tony Wang · e88009d5 · Nov 12, 2025 · 983 filesMessage 45 · ThinInformational 15Details
Commit message · Tony Wang

add detection for MSVC/2026

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 pathsigning or wallet pathauthentication path
AI analysis · Informational 15/100

This 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.

Security candidateImproved compatibility for automatically enabling huge pages on Linux systems without NUMA support.by XMRig · 5115597e · Nov 6, 2025 · 2 filesMessage 50 · ThinInformational 17Details
Commit message · XMRig

Improved compatibility for automatically enabling huge pages on Linux systems without NUMA support.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100

This 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.

Security candidatefeat: initial support for haikuby user0-07161 · b02519b9 · Nov 4, 2025 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · user0-07161

feat: initial support for haiku

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This 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.

Security candidateRemoved unused filesby SChernykh · 27c8e609 · Oct 22, 2025 · 4 filesMessage 28 · OpaqueInformational 15Details
Commit message · SChernykh

Removed unused files

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

This 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.

Security candidateRISC-V: test for instruction extensionsby SChernykh · 985fe06e · Oct 22, 2025 · 4 filesMessage 55 · ThinInformational 14Details
Commit message · SChernykh

RISC-V: test for instruction extensions

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

This 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.

Security candidateRISC-V JIT compilerby SChernykh · 75b63ddd · Oct 22, 2025 · 9 filesMessage 28 · OpaqueInformational 18Details
Commit message · SChernykh

RISC-V JIT compiler

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 18/100

This 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).

Security candidateRISC-V Intergrationby slayingripper · 643b65f2 · Oct 22, 2025 · 30 filesMessage 28 · OpaqueInformational 19Details
Commit message · slayingripper

RISC-V Intergration

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 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.

Security candidateAdded Zen4 (Hawk Point) CPUs detectionby SChernykh · da5a5674 · Oct 15, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · SChernykh

Added Zen4 (Hawk Point) CPUs detection

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

This 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.

Security candidateFix: correct FCMP++ version numberby SChernykh · a659397c · Oct 5, 2025 · 1 fileMessage 57 · ThinLow 32Details
Commit message · SChernykh

Fix: correct FCMP++ version number

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 32/100

This 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.

Security candidateSolo mining: added support for FCMP++ hardforkby SChernykh · da683d8c · Oct 5, 2025 · 3 filesMessage 45 · ThinInformational 19Details
Commit message · SChernykh

Solo mining: added support for FCMP++ hardfork

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 19/100

This 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.