https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-10-08T16:00:05.316076+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/fkie_cve-2026-104891 fkie_cve-2026-104891 2026-10-08T16:00:05.388572+00:00

mppx-condition-gate provides conditional free-access wrappers for mppx payment methods. Prior to @insumermodel/mppx-condition-gate 3.0.0 and @insumermodel/mppx-token-gate 1.0.4, the packages read a wallet address from the client-supplied credential.source, checked whether that public address met configured on-chain conditions, and returned a successful free-access receipt without invoking the wrapped payment verifier or proving that the caller controlled the wallet. An unauthenticated attacker could name any qualifying wallet and obtain content that should require payment, and cached grants could be reused for the configured cache lifetime. The corrected packages prevent free-access authorization unless payer control has been established. These issues are fixed in @insumermodel/mppx-condition-gate 3.0.0 and @insumermodel/mppx-token-gate 1.0.4.

 https://db.gcve.eu/vuln/ghsa-jg6q-3qfh-r9f8 GHSA-jg6q-3qfh-r9f8 — mppx-condition-gate: Free-access path grants on a self-declared wallet without proving control 2026-10-08T16:00:05.388682+00:00

Affected: npm: @insumermodel/mppx-condition-gate, npm: @insumermodel/mppx-token-gate

### 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 aff…