How many CVEs have patched verify?

2 published CVEs changed verify in ZenHive/mpp, in 2 distinct patches totalling 10 changed lines, between 2026 and 2026.

What is the latest CVE that changed verify?

CVE-2026-87119 (mpp Tempo subscription key authorization is not bound to the issuing challenge, allowing a captured activation credential to be replayed), published 2026-09-22, changed lines 280 to 283 of lib/mpp/methods/tempo.ex.

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

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

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

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Zenhive
Mpp
Verify

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Zenhive
Mpp
Verify

verify in ZenHive/mpp: Patched by 2 CVEs

ZenHive/mpp

Function

verify

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

lib/mpp/methods/tempo.ex

Last patched September 22, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

verify in ZenHive/mpp was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 10 lines in total.

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

CVEs that patched it

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

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References

mpp Tempo subscription key authorization is not bound to the issuing challenge, allowing a captured activation credential to be replayed
CVE-2026-87119 · lines 280–283 · +4 −0
High · CVSS 8.2
EPSS 0.6%2026-09-22
mpp Tempo keys its pre-broadcast dedup reserve on the caller-supplied transaction encoding, so a re-encoded signed transaction reserves a second slot
CVE-2026-88255 · lines 122–138 · +5 −1 in 2 hunks
Medium · CVSS 6.3
EPSS 0.5%2026-09-16

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.

1maybe_validate_fee_payer_economicslib/mpp/methods/tempo.ex3 CVEs · 3 patches2026
2broadcast_and_verifylib/mpp/methods/tempo.ex2 CVEs · 2 patches2026
3canonicalize_transactionlib/mpp/methods/tempo.ex1 CVEs · 1 patches2026
4challenge_method_detailslib/mpp/methods/tempo.ex1 CVEs · 1 patches2026
5check_hash_unusedlib/mpp/methods/tempo.ex1 CVEs · 1 patches2026
6credential_typeslib/mpp/methods/tempo.ex1 CVEs · 1 patches2026
7mark_hash_usedlib/mpp/methods/tempo.ex1 CVEs · 1 patches2026
8prepare_sponsored_transactionlib/mpp/methods/tempo.ex1 CVEs · 1 patches2026

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 validate_intent2 CVEs · lib/mpp/plug.ex intent_name2 CVEs · lib/mpp/plug.ex challenge2 CVEs · lib/mpp/telemetry.ex

All patched functions in ZenHive/mpp

Frequently asked questions

Common questions about CVE fixes to verify.

How many CVEs have patched verify?: 2 published CVEs changed verify in ZenHive/mpp, in 2 distinct patches totalling 10 changed lines, between 2026 and 2026.
What is the latest CVE that changed verify?: CVE-2026-87119 (mpp Tempo subscription key authorization is not bound to the issuing challenge, allowing a captured activation credential to be replayed), published 2026-09-22, changed lines 280 to 283 of lib/mpp/methods/tempo.ex.
How does verify compare to the rest of ZenHive/mpp?: ZenHive/mpp has 13 CVEs with a located fix in total; 2 of them changed verify.
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

lib/mpp/methods/tempo.ex on GitHub (opens in a new tab)
All patched functions in ZenHive/mpp
Patched functions directory

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