Vulnerabilities in pkg:npm/@insumermodel/mppx-condition-gate

PACKAGE
Advisory Identifier: GHSA-jg6q-3qfh-r9f8
Advisory Summary

CVE-2026-104891 is a HIGH (CVSS 7.5) free-access path grants on a vulnerability (CWE-863: Incorrect Authorization) affecting mppx-condition-gate libraries in the npm ecosystem. The issue involves free-access path grants on a self-declared wallet without proving control. Remediation is available by upgrading affected packages to version 3.0.0, 1.0.4.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@insumermodel/mppx-condition-gate

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@insumermodel/mppx-condition-gate. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-jg6q-3qfh-r9f8 CVE-2026-104891 HIGH mppx-condition-gate: Free-access path grants on a self-declared wallet without proving control

CVE-2026-104891 at a Glance

CVE Identifier CVE-2026-104891
GHSA Identifier GHSA-jg6q-3qfh-r9f8
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-863: Incorrect Authorization
Affected Product mppx-condition-gate
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-104891

To remediate this vulnerability, upgrade all affected mppx-condition-gate dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@insumermodel/mppx-condition-gate fixed: 3.0.0
npm install @insumermodel/mppx-condition-gate@3.0.0
@insumermodel/mppx-token-gate fixed: 1.0.4
npm install @insumermodel/mppx-token-gate@1.0.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @insumermodel/mppx-condition-gate

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-104891, inspect your project dependencies using npm:

npm ls @insumermodel/mppx-condition-gate

Analyze the terminal output to locate any version of mppx-condition-gate in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.0), your application is affected.

Note: The npm ls @insumermodel/mppx-condition-gate command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In mppx-condition-gate, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 state that methods relying on it "must validate the relationship to the credential payload". These packages did not. **This is a defect in these wrapper packages, not in the attestation they consume.** The attestation answers one question — does this wallet satisfy these conditions — and answered it honestly about the address it was given. Binding that address to the caller was the wrapper's responsibility. ### Affected versions Every published version of both packages is affected. The vulnerable control flow is present from the first release of each. ### Patches Fixed releases will not grant free access unless the payer has been proven, and fall through to the paid path wherever no proven payer is available. ### Workarounds Remove the condition gate from the payment method until a fixed version is installed, so all requests take the normal paid path. Alternatively, ensure the wrapped payment method has already bound the credential to the payer before the gate is consulted. ### Credit Reported by @chenshj73, who identified the issue, traced the exact code path, and proposed correct remediations.

CVE-2026-104891 Affected mppx-condition-gate Versions

2 component(s)
Fixed Versions:
3.0.01.0.4
Product / Package Ecosystem Affected Versions Fixed Version
@insumermodel/mppx-condition-gate
npm
< 3.0.0
3.0.0
@insumermodel/mppx-token-gate
npm
< 1.0.4
1.0.4

References

Frequently Asked Questions

What is CVE-2026-104891?
CVE-2026-104891 is a security vulnerability in mppx-condition-gate involving Free-access path grants on a self-declared wallet without proving control under CWE-863: Incorrect Authorization.
Which mppx-condition-gate versions are affected?
Affected versions include releases prior to 3.0.0, 1.0.4 across affected packages: @insumermodel/mppx-condition-gate, @insumermodel/mppx-token-gate.
What version fixes CVE-2026-104891?
Upgrading to 3.0.0, 1.0.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @insumermodel/mppx-condition-gate affected?
Yes, @insumermodel/mppx-condition-gate is affected in releases prior to 3.0.0. Upgrade your dependency to 3.0.0 or later.
Is @insumermodel/mppx-token-gate affected?
Yes, @insumermodel/mppx-token-gate is affected in releases prior to 1.0.4. Upgrade your dependency to 1.0.4 or later.
What is the CVSS score of CVE-2026-104891?
CVE-2026-104891 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-104891?
CVE-2026-104891 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check npm dependencies for CVE-2026-104891?
Run the dependency tree command: 'npm ls @insumermodel/mppx-condition-gate'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jg6q-3qfh-r9f8",
  "modified" : "2026-10-07T18:03:42Z",
  "published" : "2026-10-07T18:03:42Z",
  "aliases" : [ "CVE-2026-104891" ],
  "summary" : "mppx-condition-gate: Free-access path grants on a self-declared wallet without proving control",
  "details" : "### Impact\n\nBoth packages wrap an `mppx` payment method so that a wallet meeting on-chain conditions is granted free access instead of being charged.\n\nThe 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.\n\nBecause 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.\n\nmppx documents this requirement explicitly. Its type definitions describe `source` as \"an asserted identity, not independent proof of control\", and state that methods relying on it \"must validate the relationship to the credential payload\". These packages did not.\n\n**This is a defect in these wrapper packages, not in the attestation they consume.** The attestation answers one question — does this wallet satisfy these conditions — and answered it honestly about the address it was given. Binding that address to the caller was the wrapper's responsibility.\n\n### Affected versions\n\nEvery published version of both packages is affected. The vulnerable control flow is present from the first release of each.\n\n### Patches\n\nFixed releases will not grant free access unless the payer has been proven, and fall through to the paid path wherever no proven payer is available.\n\n### Workarounds\n\nRemove the condition gate from the payment method until a fixed version is installed, so all requests take the normal paid path. Alternatively, ensure the wrapped payment method has already bound the credential to the payer before the gate is consulted.\n\n### Credit\n\nReported by @chenshj73, who identified the issue, traced the exact code path, and proposed correct remediations.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@insumermodel/mppx-condition-gate"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.0.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.0.3"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@insumermodel/mppx-token-gate"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/douglasborthwick-crypto/mppx-condition-gate/security/advisories/GHSA-jg6q-3qfh-r9f8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/insumerapi/mppx-condition-gate/security/advisories/GHSA-jg6q-3qfh-r9f8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-104891"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/insumerapi/mppx-condition-gate/commit/b1d9935a57ba6d32da49eead1bfb459ad0cd55ab"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/insumerapi/mppx-condition-gate/commit/ec43a2fcd443a0fa102b6d4203abed2b785bd954"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/douglasborthwick-crypto/mppx-condition-gate"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-290", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-07T18:03:42Z",
    "nvd_published_at" : "2026-10-05T16:17:06Z"
  }
}