Defined in 2 files
Last patched
future_valid_before in ZenHive/mpp was changed by 2 published CVE fixes in 2026, in 1 distinct patches that added or removed 80 lines in total.
The name occurs in 2 files: test/mpp/methods/tempo_full_flow_test.exs, test/mpp/methods/tempo_test.exs.
ZenHive/mpp has 13 CVEs with a located fix in total, so 15% of them touched this function.
Every published CVE whose fix changed future_valid_before, newest first, with the lines each fix touched.
CVE-2026-59694 · test/mpp/methods/tempo_full_flow_test.exs · lines 163–309 · +17 −3 in 2 hunks
CVE-2026-59694 · test/mpp/methods/tempo_test.exs · lines 1580–1622 · +17 −3 in 2 hunks
CVE-2026-59695 · test/mpp/methods/tempo_full_flow_test.exs · lines 163–309 · +17 −3 in 2 hunks
CVE-2026-59695 · test/mpp/methods/tempo_test.exs · lines 1580–1622 · +17 −3 in 2 hunks
Get an alert when the next CVE fix lands in ZenHive/mpp, with the patched functions.
Monitor mpp CVEsFunctions in the same files that CVE fixes also changed.
Functions in ZenHive/mpp changed by the most CVE fixes.
Common questions about CVE fixes to future_valid_before.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
