How many CVEs have patched check_validity_window?

1 published CVEs changed check_validity_window in ZenHive/mpp, in 1 distinct patches totalling 3 changed lines, between 2026 and 2026.

What is the latest CVE that changed check_validity_window?

CVE-2026-73541 (Tempo fee sponsorship in mpp bounds each transaction but not aggregate exposure, allowing concurrent sponsor-wallet drain), published 2026-08-19, changed lines 312 to 313 of lib/mpp/methods/tempo/fee_payer_policy.ex.

How does check_validity_window compare to the rest of ZenHive/mpp?

ZenHive/mpp has 13 CVEs with a located fix in total; 1 of them changed check_validity_window.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

ZenHive/mpp

Function

check_validity_window

Name: check_validity_window in ZenHive/mpp: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/mpp/methods/tempo/fee_payer_policy.ex

Last patched August 19, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

3

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

check_validity_window in ZenHive/mpp was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 3 lines in total.

ZenHive/mpp has 13 CVEs with a located fix in total, so 8% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed check_validity_window, newest first, with the lines each fix touched.

Tempo fee sponsorship in mpp bounds each transaction but not aggregate exposure, allowing concurrent sponsor-wallet drain
CVE-2026-73541 · lines 312–313 · +2 −1
High · CVSS 8.3
EPSS 0.6%2026-08-19

Get an alert when the next CVE fix lands in ZenHive/mpp, with the patched functions.

Monitor mpp CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in ZenHive/mpp changed by the most CVE fixes.

maybe_validate_fee_payer_economics3 CVEs · lib/mpp/methods/tempo.ex non_neg_integer3 CVEs · lib/mpp/methods/tempo/fee_payer_policy.ex map2 CVEs · lib/mpp/plug.ex verify2 CVEs · lib/mpp/methods/tempo.ex validate_intent2 CVEs · lib/mpp/plug.ex intent_name2 CVEs · lib/mpp/plug.ex

All patched functions in ZenHive/mpp

Frequently asked questions

Common questions about CVE fixes to check_validity_window.

How many CVEs have patched check_validity_window?: 1 published CVEs changed check_validity_window in ZenHive/mpp, in 1 distinct patches totalling 3 changed lines, between 2026 and 2026.
What is the latest CVE that changed check_validity_window?: CVE-2026-73541 (Tempo fee sponsorship in mpp bounds each transaction but not aggregate exposure, allowing concurrent sponsor-wallet drain), published 2026-08-19, changed lines 312 to 313 of lib/mpp/methods/tempo/fee_payer_policy.ex.
How does check_validity_window compare to the rest of ZenHive/mpp?: ZenHive/mpp has 13 CVEs with a located fix in total; 1 of them changed check_validity_window.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track ZenHive/mpp CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing