CVE-2026-82751
HIGHDescription
Improper Validation of Specified Quantity in Input in ZenHive mpp allows an unauthenticated remote client to inflate the fee-payer's gas cost per sponsored payment by a large multiplier and to have the sponsor pay for provisioning an access key on the client's own account. When the server sponsors Tempo payments, MPP.Methods.Tempo.FeePayerPolicy.measure/3 in lib/mpp/methods/tempo/fee_payer_policy.ex bounds the gas fields, the fee budget, the validity window and the access list of the client-signed 0x76 envelope, but does not check whether the envelope carries the optional key_authorization field. A client can attach a fully signed key authorization, provisioning a new access key with token spending limits on its own account, alongside the normal payment call. The key and each limit entry are persistent storage writes billed as intrinsic gas to the sponsor, bounded only by the gas_limit ceiling. At the reporter's default of one key with three token limits the sponsored cost rises from about 46,587 gas to about 1,808,700 gas, and the client keeps a valid access key it paid nothing for. This issue affects mpp: from 0.2.0 before 0.16.1.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 26% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1284 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-20699 | Critical | 10.0 | 72% | KEV | - |
| CVE-2021-43267 | Critical | 9.8 | 58% | - | Fix |
| CVE-2022-31629 | Medium | 6.5 | 49% | - | Fix |
| CVE-2025-9316 | Unscored | - | 36% | - | - |
| CVE-2022-36620 | High | 7.5 | 24% | - | - |
| CVE-2008-1440 | High | 7.1 | 23% | - | - |
Common questions
How do I fix CVE-2026-82751?
No published fix for CVE-2026-82751 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-82751 being actively exploited?
Not that we know of. CVE-2026-82751 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.33% is the estimated probability that it will be exploited in the next 30 days. That is higher than 26% of all scored CVEs.
How severe is CVE-2026-82751?
CVE-2026-82751 has a CVSS v4 base score of 8.3, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-82751
Markdown
[](https://tridentstack.com/cve/CVE-2026-82751)HTML
<a href="https://tridentstack.com/cve/CVE-2026-82751"><img src="https://tridentstack.com/cve/badge/CVE-2026-82751.svg" alt="CVE-2026-82751"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-08.