-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 0xCERT Security Advisory 0xCERT-2026-0367 ============================================================ Advisory-ID: 0xCERT-2026-0367 Severity: Medium Published: 2026-11-17T20:04:56.000Z Updated: 2026-11-17T20:43:51.554Z Chains: Other / Multi-chain URL: https://www.0xcert.com/advisory/0xCERT-2026-0367 Title: pympp fee-payer policy ignores calldata length, letting clients drain a sponsoring server's Tempo fee wallet Summary - ------- pympp before 0.9.1 (Tempo Machine Payments Protocol, Python) does not bound calldata length when the server sponsors fees, so padded calldata inflates gas costs and drains the fee-payer wallet. Upgrade to 0.9.1. Details - ------- Summary pympp, the Python SDK for the Machine Payments Protocol on the Tempo chain, can act as a fee payer that cosigns and broadcasts client transactions. Its FeePayerPolicy caps gas_limit (2M) and max_fee_per_gas (100 Gwei) but does not check calldata length, and calldata is validated with lenient eth_abi decoding that accepts trailing bytes. Per the advisory, padded calldata inflates the fees the server pays. Affected - - pympp (PyPI) < 0.9.1 (the advisory describes the code path in 0.8.0) - - Fixed in 0.9.1 Impact When the server acts as fee_payer, a client can append non-zero padding bytes to otherwise valid calldata. Tempo uses legacy calldata gas pricing (16 gas per non-zero byte), so the actual fee rises while gas_limit and max_fee_per_gas stay within policy caps. The server cosigns and broadcasts the transaction, draining its fee-payer wallet. GitHub rates the issue Moderate (CVSS 4.0: AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N). The advisory does not report exploitation in the wild. Recommended actions - - Upgrade pympp to 0.9.1 or later on any server that sponsors transaction fees. - - Until upgraded, disable fee sponsorship or keep only a small balance in the fee-payer wallet, and monitor its spend. Source & attribution This 0xCERT advisory summarises GitHub Security Advisory GHSA-v858-xh7w-8jr5 (CVE-2026-63634) published by the tempoxyz/pympp maintainers: https://github.com/tempoxyz/pympp/security/advisories/GHSA-v858-xh7w-8jr5, as mirrored by OSV. Details may change; refer to the original source for the authoritative record. References - ---------- - - https://github.com/tempoxyz/pympp/security/advisories/GHSA-v858-xh7w-8jr5 - - CVE-2026-63634 - - https://osv.dev/vulnerability/GHSA-v858-xh7w-8jr5 - - https://github.com/tempoxyz/pympp/commit/57a750d0d980b8e6c3bea62a40b7621f176ff1f0 - - https://github.com/tempoxyz/pympp/releases/tag/v0.9.1 Verify with the 0xCERT OpenPGP key: https://www.0xcert.com/pgp.asc Fingerprint: 5F94 3ED1 1E50 CF31 2128 C493 CCC7 D9EC 9415 723D -----BEGIN PGP SIGNATURE----- wrsEARYKAG0Fgmr+AssJEDe9Tbcr+ZxrRRQAAAAAABwAIHNhbHRAbm90YXRp b25zLm9wZW5wZ3Bqcy5vcmcrxQJ3CmlC8exzUSInQZVmu6Yq51wNsw4oKExr ZnBEBBYhBGCkkFZbJcT5QWu27ze9Tbcr+ZxrAAAZ7AD/S+/7bhZKE9jF4c4c iIT2N20tFOjzxmzdFSloBfubb2QBANPGBVoZsJVdoH/6fQ6WiG3OxLFjAUsi nou2DEggp9oP =Ct2B -----END PGP SIGNATURE-----