Uncaught Panic in ORML Rewards Pallet

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary A vulnerability in the addshare function of the Rewards pallet (part of the ORML repository) can lead to an uncaught Rust panic when handling user-provided input exceeding the u128 range. Affected Components - ORML Rewards pallet (rewards/src/lib.rs) - Any Substrate-based chain using ORML Rewards with addshare accepting unvalidated large u128 inputs Technical Details - addshare performs arithmetic on user-supplied values (addamount) of type T::Share (mapped to u128 in Acala). - If addamount is large enough (e.g., i128::MAX), the intermediate result may overflow and panic on the cast to u128. - Validation occurs only after arithmetic, enabling a crafted input to trigger an overflow. Impact A malicious user submitting a specially crafted extrinsic can cause a panic in the runtime: - Denial of Service by crashing the node process. - Potential for invalid blocks produced by validators. Likelihood This issue is exploitable in production if there exists at least one rewards pool…

Published by the source

14 Feb 2025, 17:26 UTC

Last modified by the source

14 Feb 2025, 17:26 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5v93-9mqw-p9mh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5v93-9mqw-p9mh

Advisory: Uncaught Panic in ORML Rewards Pallet
IDs: GHSA-5v93-9mqw-p9mh
Record: https://patchnext.com/advisories/ghsa-5v93-9mqw-p9mh (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: orml-rewards 1.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io orml-rewards: affected < 1.2.1; fixed in 1.2.1

## Suggested inspection (read-only)
- crates.io orml-rewards: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on orml-rewards.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5v93-9mqw-p9mh (GitHub-reviewed advisory GHSA-5v93-9mqw-p9mh lists affected ranges: crates.io orml-rewards >=0 <1.2.1)

Commands are suggestions: review each one before running it.