mppx-condition-gate: Free-access path grants on a self-declared wallet without proving control

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-104891: 0.28% estimated exploitation activity in the next 30 days; percentile 20.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Both packages wrap an mppx payment method so that a wallet meeting on-chain conditions is granted free access instead of being charged. The free-access path reads the payer address from credential.source — a client-supplied DID in the payment credential — asks InsumerAPI whether that address satisfies the configured conditions, and on a pass returns a successful receipt without ever calling the wrapped payment verifier. Nothing in that path establishes that the caller controls the wallet it named. Because qualifying wallets are public chain state, an attacker does not need to guess one. Naming any qualifying address in credential.source is sufficient to obtain free access to a route that should have been paid for. An in-process cache (default TTL 300s, keyed on wallet and conditions) then re-serves the grant without re-evaluating. mppx documents this requirement explicitly. Its type definitions describe source as "an asserted identity, not independent proof of control", and…

Published by the source

7 Oct 2026, 18:03 UTC

Last modified by the source

7 Oct 2026, 18:15 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jg6q-3qfh-r9f8

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-jg6q-3qfh-r9f8

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-jg6q-3qfh-r9f8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-104891

Advisory: mppx-condition-gate: Free-access path grants on a self-declared wallet without proving control
IDs: CVE-2026-104891, GHSA-jg6q-3qfh-r9f8
Record: https://patchnext.com/advisories/cve-2026-104891 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @insumermodel/mppx-condition-gate 3.0.0; @insumermodel/mppx-token-gate 1.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @insumermodel/mppx-condition-gate: affected <= 2.0.3; fixed in 3.0.0
- npm @insumermodel/mppx-token-gate: affected <= 1.0.3; fixed in 1.0.4

## Suggested inspection (read-only)
- `npm ls @insumermodel/mppx-condition-gate --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @insumermodel/mppx-token-gate --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @insumermodel/mppx-condition-gate, @insumermodel/mppx-token-gate.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jg6q-3qfh-r9f8 (GitHub-reviewed advisory GHSA-jg6q-3qfh-r9f8 lists affected ranges: npm @insumermodel/mppx-condition-gate >=0 =0 <=1.0.3)
- Verified: https://osv.dev/vulnerability/GHSA-jg6q-3qfh-r9f8 (OSV record GHSA-jg6q-3qfh-r9f8 lists affected ranges: npm @insumermodel/mppx-condition-gate >=0 =0 <1.0.4 (fixed))

Commands are suggestions: review each one before running it.