Report a vulnerability in Lantern

Everything you submit is treated as untrusted data. Claude checks the code you cite and replays your proof of concept against a sandboxed copy of Lantern; a maintainer makes every money decision. Read the program rules first.

Trying it out? Load an example:

Step 1

Free report or bounty claim?

Reporting is always free. Claiming a bounty takes a refundable hold, so only claims someone stands behind cost anything.

Free reportBest effort. No deposit and no bounty. Triage still runs, and maintainers see the result.Bounty claimPost a refundable $20.00 PayPal hold. Reproduced reports are paid from the bounty table below.

low $50.00medium $200.00high $500.00critical $1,500.00

Step 2

The issue

Cite real files and functions: Good Faith checks every one exists at the version you name.

Title

Affected version

In scope: 1.4.0, 1.4.1

Claimed severityoptional

Affected codeoptional

One per line, e.g. - `src/notes.ts`, `registerNoteRoutes()`

Description

Impactoptional

Step 3

Proof of concept

HTTP steps replay against a fresh, sandboxed Lantern with seeded canary secrets. A leaked canary is proof.

1.act as

The sandbox signs each step in as the chosen account; Host, Cookie and Authorization are set for you.

alice: the researcher's own test account (a normal user)
bob: a second normal user, the victim in access-control tests
admin: the Lantern administrator

Step 4

You

Researcher handle

Shown on the hall of fame if you are paid.

PayPal email for the bountyoptional

Leave empty to pay the PayPal account that posts the deposit.

Post the $20.00 deposit and submit

PayPal places an authorization hold; nothing is charged. It is released in full for any honest report, including duplicates, and captured only if a maintainer confirms the report is fabricated. Triage starts the moment the hold is in place.

Loading PayPal