CVE-2026-34209: CWE-294: Authentication Bypass by Capture-replay in wevm mppx
mppx is a TypeScript interface for machine payments protocol. Prior to version 0.4.11, the tempo/session cooperative close handler validated the close voucher amount using "<" instead of "<=" against the on-chain settled amount. An attacker could submit a close voucher exactly equal to the settled amount, which would be accepted without committing any new funds, effectively closing or griefing the channel for free. This issue has been patched in version 0.4.11.
AI Analysis
Technical Summary
CVE-2026-34209 is an authentication bypass vulnerability categorized under CWE-294 affecting the mppx TypeScript interface of the wevm project, which implements a machine payments protocol. The vulnerability arises from an off-by-one logic error in the tempo/session cooperative close handler prior to version 0.4.11. Specifically, the handler validates the close voucher amount against the on-chain settled amount using a strict less-than comparison ('<') rather than a less-than-or-equal ('<=') comparison. This subtle difference allows an attacker to submit a close voucher whose amount exactly matches the settled amount, which the system erroneously accepts without requiring any additional funds to be committed. Consequently, an attacker can close or grief a payment channel for free, effectively bypassing the intended authentication and fund validation mechanisms. The vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. Although no known exploits are currently reported in the wild, the flaw poses a significant risk to the integrity of payment channels by allowing unauthorized channel closure. The issue was addressed and patched in version 0.4.11 of mppx by correcting the comparison operator to properly validate close vouchers. This vulnerability has a CVSS v3.1 base score of 7.5, reflecting its high severity due to ease of exploitation and impact on data integrity.
Potential Impact
The primary impact of CVE-2026-34209 is on the integrity of payment channels managed by the mppx interface in the wevm project. Attackers can exploit this vulnerability to close payment channels without committing the required funds, potentially causing financial loss or denial of service by griefing channels. This can disrupt automated machine payment workflows and damage trust in the payment protocol. Since the vulnerability does not affect confidentiality or availability directly, the risk is mainly financial and operational. Organizations relying on mppx for machine-to-machine payments or blockchain-based settlements may face unauthorized channel closures, leading to transaction disputes, reconciliation issues, and potential loss of funds. The ease of exploitation without authentication or user interaction increases the threat level, especially in environments where mppx is exposed to untrusted networks. Although no active exploits are known, the vulnerability's presence in widely used versions prior to 0.4.11 means that attackers could develop exploits, increasing the urgency for remediation.
Mitigation Recommendations
To mitigate CVE-2026-34209, organizations should immediately upgrade all deployments of the wevm mppx interface to version 0.4.11 or later, where the vulnerability has been patched. Beyond upgrading, it is recommended to audit all payment channel closing logic to ensure proper validation of voucher amounts, specifically verifying that comparison operators correctly enforce expected conditions. Implement additional monitoring and alerting for unusual channel closure patterns that could indicate exploitation attempts or griefing. Employ network segmentation and access controls to limit exposure of mppx interfaces to trusted entities only. Consider integrating multi-factor verification or cryptographic proofs for channel closure requests to strengthen authentication beyond voucher amount checks. Regularly review and update dependencies and third-party components to incorporate security patches promptly. Finally, conduct security testing and code reviews focused on boundary conditions and off-by-one errors in financial transaction code to prevent similar vulnerabilities.
Affected Countries
United States, Germany, South Korea, Japan, United Kingdom, Canada, Singapore, Switzerland, Netherlands, Australia
CVE-2026-34209: CWE-294: Authentication Bypass by Capture-replay in wevm mppx
Description
mppx is a TypeScript interface for machine payments protocol. Prior to version 0.4.11, the tempo/session cooperative close handler validated the close voucher amount using "<" instead of "<=" against the on-chain settled amount. An attacker could submit a close voucher exactly equal to the settled amount, which would be accepted without committing any new funds, effectively closing or griefing the channel for free. This issue has been patched in version 0.4.11.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-34209 is an authentication bypass vulnerability categorized under CWE-294 affecting the mppx TypeScript interface of the wevm project, which implements a machine payments protocol. The vulnerability arises from an off-by-one logic error in the tempo/session cooperative close handler prior to version 0.4.11. Specifically, the handler validates the close voucher amount against the on-chain settled amount using a strict less-than comparison ('<') rather than a less-than-or-equal ('<=') comparison. This subtle difference allows an attacker to submit a close voucher whose amount exactly matches the settled amount, which the system erroneously accepts without requiring any additional funds to be committed. Consequently, an attacker can close or grief a payment channel for free, effectively bypassing the intended authentication and fund validation mechanisms. The vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. Although no known exploits are currently reported in the wild, the flaw poses a significant risk to the integrity of payment channels by allowing unauthorized channel closure. The issue was addressed and patched in version 0.4.11 of mppx by correcting the comparison operator to properly validate close vouchers. This vulnerability has a CVSS v3.1 base score of 7.5, reflecting its high severity due to ease of exploitation and impact on data integrity.
Potential Impact
The primary impact of CVE-2026-34209 is on the integrity of payment channels managed by the mppx interface in the wevm project. Attackers can exploit this vulnerability to close payment channels without committing the required funds, potentially causing financial loss or denial of service by griefing channels. This can disrupt automated machine payment workflows and damage trust in the payment protocol. Since the vulnerability does not affect confidentiality or availability directly, the risk is mainly financial and operational. Organizations relying on mppx for machine-to-machine payments or blockchain-based settlements may face unauthorized channel closures, leading to transaction disputes, reconciliation issues, and potential loss of funds. The ease of exploitation without authentication or user interaction increases the threat level, especially in environments where mppx is exposed to untrusted networks. Although no active exploits are known, the vulnerability's presence in widely used versions prior to 0.4.11 means that attackers could develop exploits, increasing the urgency for remediation.
Mitigation Recommendations
To mitigate CVE-2026-34209, organizations should immediately upgrade all deployments of the wevm mppx interface to version 0.4.11 or later, where the vulnerability has been patched. Beyond upgrading, it is recommended to audit all payment channel closing logic to ensure proper validation of voucher amounts, specifically verifying that comparison operators correctly enforce expected conditions. Implement additional monitoring and alerting for unusual channel closure patterns that could indicate exploitation attempts or griefing. Employ network segmentation and access controls to limit exposure of mppx interfaces to trusted entities only. Consider integrating multi-factor verification or cryptographic proofs for channel closure requests to strengthen authentication beyond voucher amount checks. Regularly review and update dependencies and third-party components to incorporate security patches promptly. Finally, conduct security testing and code reviews focused on boundary conditions and off-by-one errors in financial transaction code to prevent similar vulnerabilities.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-26T15:57:52.324Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69cbd8dae6bfc5ba1d1c3123
Added to database: 3/31/2026, 2:23:22 PM
Last enriched: 3/31/2026, 2:39:18 PM
Last updated: 4/1/2026, 3:52:16 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.