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

fix: harden SSRF checks and use explicit local LNURL route opt-ins (#4313)

Public commit record

What the developer wrote

Authored by Arc

70/100 · Adequate
fix: harden SSRF checks and use explicit local LNURL route opt-ins (#4313)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit is a security hardening patch for LNbits, a Bitcoin Lightning wallet platform. It fixes weaknesses in the server's outgoing web-request protections (SSRF, or Server-Side Request Forgery) that could let an attacker trick the LNbits server into making requests to internal or cloud metadata addresses, potentially stealing funds or secrets. The patch also replaces a fixed internal list of allowed local LNURL paths with an explicit opt-in marker on each route, so only intentionally exposed endpoints can be reached internally. The vendor says every version before 1.7.0 is affected, funds are at risk, and operators must rotate keys/secrets after upgrading.

Recommended action

Upgrade to LNbits v1.7.0 or later immediately. Because the vendor states exposed credentials may remain usable after patching, also rotate all LNbits admin keys, wallet keys, API secrets, and any linked external service credentials. Review server logs for unexpected outbound requests to internal/cloud metadata addresses before the upgrade.

Security signals we found

01

SSRF hardening: multicast, IPv6 transition/embedded addresses, and EC2 IPv6 metadata endpoint blocked

02

Local LNURL routing moved from hard-coded regex allow-list to explicit per-route openapi_extra opt-in

03

Backslash path traversal blocked in private HTTP endpoint checks

04

In-process local LNURL requests stripped of Authorization/Cookie headers and avoid DNS resolution

05

Vendor security release (v1.7.0) states pre-1.7.0 versions affected, funds at risk, requires key/secret rotation

Risk score

Why this scored 89/100

Our methodology →
Potential impact 28/30
Exploitability 22/25
Stealth signal 12/15
Affected reach 13/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

Harden SSRF checks and require explicit local LNURL opt-ins

Follow-up incident hardening that strengthens SSRF checks and changes local LNURL routing from an implicit exception to explicit route-level opt-ins. It was merged into v1.7.0 before the urgent security release.

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.