How many CVEs have patched broadcast_reserved_transaction?

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

What is the latest CVE that changed broadcast_reserved_transaction?

CVE-2026-88255 (mpp Tempo keys its pre-broadcast dedup reserve on the caller-supplied transaction encoding, so a re-encoded signed transaction reserves a second slot), published 2026-09-16, changed lines 1010 of lib/mpp/methods/tempo.ex.

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

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

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

broadcast_reserved_transaction

Name: broadcast_reserved_transaction 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 16, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

broadcast_reserved_transaction in ZenHive/mpp was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 2 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 broadcast_reserved_transaction, newest first, with the lines each fix touched.

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 · line 1010 · +1 −1
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.

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

How many CVEs have patched broadcast_reserved_transaction?: 1 published CVEs changed broadcast_reserved_transaction in ZenHive/mpp, in 1 distinct patches totalling 2 changed lines, between 2026 and 2026.
What is the latest CVE that changed broadcast_reserved_transaction?: CVE-2026-88255 (mpp Tempo keys its pre-broadcast dedup reserve on the caller-supplied transaction encoding, so a re-encoded signed transaction reserves a second slot), published 2026-09-16, changed lines 1010 of lib/mpp/methods/tempo.ex.
How does broadcast_reserved_transaction compare to the rest of ZenHive/mpp?: ZenHive/mpp has 13 CVEs with a located fix in total; 1 of them changed broadcast_reserved_transaction.
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