56 matches found
EUVD-2026-120445
pympp allows excessive sponsored transaction fees through padded calldata...
CVE-2026-63634
pympp is a Python SDK for the Machine Payments Protocol. Prior to version 0.9.1, when the server acts as the feepayer, pympp validates calldata using ethabi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gaslimit ≤ 2 M and maxfeepergas ≤ 100 Gwei but does not check...
CVE-2026-63634 pympp: Gas Draining with padding
pympp is a Python SDK for the Machine Payments Protocol. Prior to version 0.9.1, when the server acts as the feepayer, pympp validates calldata using ethabi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gaslimit ≤ 2 M and maxfeepergas ≤ 100 Gwei but does not check...
CVE-2026-63634 pympp: Gas Draining with padding
pympp is a Python SDK for the Machine Payments Protocol. Prior to version 0.9.1, when the server acts as the feepayer, pympp validates calldata using ethabi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gaslimit ≤ 2 M and maxfeepergas ≤ 100 Gwei but does not check...
CVE-2026-63634: tempoxyz pympp: pympp is a Python SDK for the Machine Payments Protocol
pympp is a Python SDK for the Machine Payments Protocol. Prior to version 0.9.1, when the server acts as the feepayer, pympp validates calldata using ethabi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gaslimit ≤ 2 M and maxfeepergas ≤ 100 Gwei but does not check...
PT-2026-141128
Name of the Vulnerable Software and Affected Versions pympp versions prior to 0.9.1 Description When the server operates as the fee payer, the software validates calldata using eth abi decoding, which does not strictly handle trailing bytes. While the FeePayerPolicy limits gas limit and max fee p...
mppx: Gas Draining with padding
Details When the server acts as the feepayer, mppx 0.6.27 validates calldata using viem's decodeFunctionData, which is lenient about trailing bytes. The FeePayerPolicy caps gaslimit ≤ 2 M and maxfeepergas ≤ 100 Gwei but does not check calldata length. Tempo uses legacy calldata gas pricing: 16 ga...
GHSA-727H-3VM5-QWQ6 mppx: Gas Draining with padding
Details When the server acts as the feepayer, mppx 0.6.27 validates calldata using viem's decodeFunctionData, which is lenient about trailing bytes. The FeePayerPolicy caps gaslimit ≤ 2 M and maxfeepergas ≤ 100 Gwei but does not check calldata length. Tempo uses legacy calldata gas pricing: 16 ga...
CVE-2026-63627 mppx: Gas Draining with padding
mppx is a TypeScript interface for machine payments protocol. Prior to 0.8.2, FeePayerPolicy in src/tempo/internal/fee-payer.ts used decodeFunctionData to validate fee-sponsored calldata but did not reject trailing bytes. A client could append nonzero padding that increased intrinsic calldata gas...
PT-2026-96974
Name of the Vulnerable Software and Affected Versions mppx versions prior to 0.8.2 Description In the FeePayerPolicy within src/tempo/internal/fee-payer.ts, the software uses the decodeFunctionData function to validate fee-sponsored calldata but fails to reject trailing bytes. A client can append...
Exploit for CVE-2026-65058
Trezor Safe Calldata Confirmation-Binding Bypass — CVE-2026-65...
Exploit for CVE-2026-65058
Trezor Safe Calldata Confirmation-Binding Bypass — CVE-2026-65...
EUVD-2026-46400
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum signtx / signtxeip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata...
CVE-2026-65058
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum signtx / signtxeip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata...
CVE-2026-65058 Trezor Safe improper security check in on-device display
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum signtx / signtxeip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata...
CVE-2026-65058 Trezor Safe improper security check in on-device display
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum signtx / signtxeip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata...
CVE-2026-65058
The CVE-2026-65058 affects Trezor Safe firmware 3, 5, and 7, where a confirmation-binding flaw in the Ethereum sign_tx / sign_tx_eip1559 flow allows an attacker to present calldata and later supply a different tail, changing the signed transaction while only the initial calldata chunk is confirme...
CVE-2026-65058 Trezor Safe improper security check in on-device display
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum signtx / signtxeip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata...
Trezor Safe improper security check in on-device display
RISK EVALUATION Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum signtx / signtxeip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could...
PT-2026-62107
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum sign tx / sign tx eip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present...