Quick answers
- Is CVE-2026-82751 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82751 being exploited in the wild.
- How severe is CVE-2026-82751?
- Informational severity, published 6 September 2026.
- Which products and versions are affected?
- ZenHive Mpp 0.2.0 through 0.16.0.
- Is there a fix for CVE-2026-82751?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82751 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82751?
- Check whether you run ZenHive Mpp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in ZenHive mpp's FeePayerPolicy.measure/3 function in lib/mpp/methods/tempo/fee_payer_policy.ex. The code validates gas limits, fee budgets, validity windows, and access lists in client-signed 0x76 envelopes, but fails to check for the optional key_authorization field. An unauthenticated remote attacker can attach a fully signed key authorization request to provision new access keys with token spending limits on their own account within a normal sponsored payment. The key provisioning and limit entries are stored as persistent state writes that are billed as intrinsic gas to the sponsor, bounded only by the gas_limit ceiling. At baseline (one key with three token limits), this inflates costs from ~46,587 gas to ~1,808,700 gas while the attacker retains a valid access key at no cost. The issue affects versions 0.2.0 through 0.16.0; version 0.16.1 and later contain fixes.
Affected products
- ZenHive mpp 0.2.0 through 0.16.0
Timeline
- 2026-09-06: disclosed