CVE-2026-87119

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Authentication Bypass by Capture-replay in ZenHive mpp allows an attacker holding a captured subscription activation credential to charge the payer repeatedly.

The payer signs a Tempo KeyAuthorization over the chain id, key type, key id, expiry, limits and scopes only, with nothing tying it to the challenge that prompted it. MPP.Methods.Tempo.KeyAuthorization.verify/3 in lib/mpp/methods/tempo/key_authorization.ex pins each of those signed fields against the subscription request, and the access key it pins is a static per-endpoint server key, so one signed authorization verifies against every challenge the server issues for the same subscription terms. MPP.Methods.Tempo.Subscription.activate/4 deduplicates activations by challenge id, so presenting the captured credential under a fresh challenge produces a different dedup key, claim_activation succeeds, and the subscription transaction is built and broadcast again. Each replay charges the payer's wallet a new first-period settlement and re-authorizes the server key, bounded only by the subscription expiry and the chain's own semantics for re-installing an existing key.

This issue affects mpp: from 0.14.0 before 0.16.2.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (5)

Auto-updated Sep 22, 2026
Patch available. Sources: github, github_commit.
github_commit

commit 4b6eaec02af0 (ZenHive/mpp)

Fix landed in ZenHive/mpp commit 4b6eaec02af0 — awaiting tagged release

https://github.com/ZenHive/mpp/commit/4b6eaec02af0e8485cfb4ff68f467d075ed5dd6f
github_commit

commit db464dfa9a86 (ZenHive/mpp)

Fix landed in ZenHive/mpp commit db464dfa9a86 — awaiting tagged release

https://github.com/ZenHive/mpp/commit/db464dfa9a86ccda58f0827101f6da6bd8aafa78
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-87119
generic

CVE-2026-87119

https://cna.erlef.org/cves/CVE-2026-87119.html
github Patch Available

Tempo subscription key authorization is not bound to the issuing challenge — a captured activation credential can be replayed under a fresh challenge; witness-bearing authorizations from current mppx clients are rejected · Advisory · ZenHive/mpp · GitHub

https://github.com/ZenHive/mpp/security/advisories/GHSA-p9fv-9w58-95x2

Vendor Advisories for CVE-2026-87119(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
mpp0.14.0, 0.15.0, 0.16.0, 0.16.10.16.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 22:58 UTCEG score recompute
  2. 2026-09-24 22:58 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 09:53 UTCGHSA enrichment
  5. 2026-09-23 20:59 UTCEG score recompute
  6. 2026-09-23 20:59 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 08:06 UTCGHSA enrichment
  9. 2026-09-22 19:12 UTCGHSA enrichment
  10. 2026-09-22 13:18 UTCEG score recompute
  11. 2026-09-22 13:18 UTCGHSA enrichment
  12. 2026-09-22 12:22 UTCEG score recompute
  13. 2026-09-22 11:21 UTCEG score recompute
  14. 2026-09-22 11:20 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-87119?
CVE-2026-87119 is a high vulnerability published on September 22, 2026. Authentication Bypass by Capture-replay in ZenHive mpp allows an attacker holding a captured subscription activation credential to charge the payer repeatedly. The payer signs a Tempo KeyAuthorization over the chain id, key type, key id, expiry, limits and scopes only, with nothing tying it to the…
When was CVE-2026-87119 disclosed?
CVE-2026-87119 was first published in the National Vulnerability Database on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87119 actively exploited?
CVE-2026-87119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.0% of all scored CVEs.
What is the CVSS score of CVE-2026-87119?
CVE-2026-87119 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-87119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-87119

Explore →

Is Your Infrastructure Affected by CVE-2026-87119?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs