CVE-2026-63634
pympp is a Python SDK for the Machine Payments Protocol. Prior to …
pympp is a Python SDK for the Machine Payments Protocol. Prior to version 0.9.1, when the server acts as the fee_payer, pympp validates calldata using eth_abi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gas_limit (≤ 2 M) and max_fee_per_gas (≤ 100 Gwei) but does not check calldata length. Tempo uses legacy calldata gas pricing: 16 gas per non-zero byte. Appending N bytes of 0x01 padding inflates actual gas used by N × 16 while keeping gas_limit and max_fee_per_gas within policy caps. The server cosigns and broadcasts the padded transaction, draining its fee-payer wallet. This issue has been patched in version 0.9.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/tempoxyz/pympp/commit/57a750d0d980b8e6c3bea62a40b7621f176ff1f0
- github.com/tempoxyz/pympp/releases/tag/v0.9.1
- github.com/tempoxyz/pympp/security/advisories/GHSA-v858-xh7w-8jr5
- nvd.nist.gov/vuln/detail/CVE-2026-63634
- github.com/advisories/GHSA-v858-xh7w-8jr5
- nvd.nist.gov/vuln/detail/CVE-2026-63634
- cve.org/CVERecord?id=CVE-2026-63634
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.