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

fix: centralize SSRF protection and block self-targeted requests (#4310)

Public commit record

What the developer wrote

Authored by Arc

85/100 · Strong
fix: centralize SSRF protection and block self-targeted requests (#4310)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>
✓ Specific, 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 major security patch for LNbits released after a November incident. It fixes two broad weaknesses: attackers could trick the server into making requests to itself or to internal/cloud services (SSRF), and new user accounts could be created too freely, letting attackers sign up and abuse those features. The patch centralizes outbound-request protections, blocks self-targeted requests, disables public registration by default, and adds activation/invitation requirements. The vendor explicitly says every version before 1.7.0 is affected and funds are at risk of theft.

Recommended action

Upgrade to LNbits v1.7.0 or later immediately. After upgrading, rotate all API keys, wallet keys, admin secrets, and any credentials that may have been exposed, because the vendor warns that exposed credentials could remain usable. Review the Security settings page to confirm outbound protection status and supply LNBITS_OUTBOUND_HOST_IPS for any public NAT/origin addresses not visible locally. Keep public registration disabled unless explicitly required, and use invitation/activation codes if it is enabled. Run the provided Docker launcher so container deployments receive host interface addresses.

Security signals we found

01

New centralized SafeHttpClient with DNS pinning, redirect limits, and destination validation

02

New outbound.py blocks requests to the instance hostname and locally assigned/supplied IP addresses

03

SSRF protection applied to LNURL, NIP-05, webhooks, WASM extension HTTP, and WebSockets

04

Private/internal/cloud metadata addresses blocked by default; administrator opt-in retained but scoped

05

Public registration disabled by default; anonymous account creation gated by settings

06

Username/password registration requires activation/invitation when configured

07

Migration m056 disables public registration on existing databases

08

Service-fee helper now only credits confirmed outgoing payments

09

Vendor advisory states pre-1.7.0 versions affected, funds at risk of theft, and credentials may remain usable after upgrade

Risk score

Why this scored 90/100

Our methodology →
Potential impact 28/30
Exploitability 22/25
Stealth signal 12/15
Affected reach 14/15
Confidence 9/10
Evidence quality 5/5
Primary-source trail

Evidence and disclosure record

Verified links used to place this patch in context. External claims remain attributed to their publishers.

Vendor advisory · Primary

Centralize SSRF protection and block self-targeted requests

Incident-response change centralizing outbound-request validation and blocking requests that resolve to the LNbits server itself. The pull request was opened hours after the November 8 shutdown warning and merged into v1.7.0.

Vendor advisory

LNbits 1.7.0 security update and recovery guidance

The vendor says every version before 1.7.0 is affected, funds are at risk of theft, and exposed credentials may remain usable after an upgrade. It requires key and secret rotation in addition to updating.

Release notes

LNbits v1.7.0 urgent security update

The first stable release containing the November incident fixes and recovery controls. LNbits instructs all operators to update immediately.

Release notes

LNbits v1.7.0 security release announcement

Official announcement that v1.7.0 is released and operators should follow the linked upgrade guidance.

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.