AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 62 Bitcoin

feat: Extensions for all (#4021)

Public commit record

What the developer wrote

Authored by Vlad Stan

80/100 · Strong
feat: Extensions for all (#4021)

Co-authored-by: alan <alan@lnbits.com>
Co-authored-by: Tiago Vasconcelos <talvasconcelos@gmail.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a large feature commit that adds a new 'WASM extensions' system to LNbits, allowing extensions to run as sandboxed WebAssembly modules instead of Python code. It introduces permission checks, runtime limits, and sandboxed APIs for storage, wallet access, HTTP requests, and background payments. Because this is a brand-new, complex subsystem touching security-critical code (payments, wallets, extension installation, admin controls), it carries significant security risk, but the commit itself is a feature addition rather than a disclosed vulnerability fix. There is no evidence in the commit or supplied references that this is a known security issue or that a CVE exists.

Recommended action

Treat this commit as a high-risk feature addition requiring thorough security review. Prioritize auditing the WASM host API (`wasm_ext/api/host.py`), permission validation (`wasm_ext/api/permissions.py`), background payment authorization (`wasm_ext/api/background_payments.py`), runtime limit enforcement, and the extension installation/activation flow. Perform fuzzing and sandbox escape testing on the WASM runtime. Do not assume the sandbox is secure without independent verification. No immediate patch is indicated because this is a feature commit, not a disclosed vulnerability fix.

Security signals we found

01

New sandboxed execution subsystem (WASM runtime) added

02

New permission model for extension capabilities

03

Background payment permission with amount and destination policy controls

04

Wallet payment watch permission added

05

Runtime limits enforced for WASM invocations, host calls, HTTP, storage, and wallet calls

06

New database migrations for permissions and runtime limits

07

Extension installation path now validates declared permissions

08

Admin-only endpoints for stopping invocations and setting runtime limits

09

No security advisory, CVE, or incident disclosure present in commit or references

Risk score

Why this scored 62/100

Our methodology →
Potential impact 18/30
Exploitability 15/25
Stealth signal 8/15
Affected reach 12/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.