Skip to content
Web

CVE-2026-86184

9.3
Critical
EPSS 0.60%Patch availableSep 8, 2026

Auth bypass in Lara Dashboard <1.3.0 lets attackers obtain authenticated sessions via screenshot-login.

common questions

Is CVE-2026-86184 being exploited?

Not confirmed. CVE-2026-86184 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.60% probability of exploitation in the next 30 days.

How severe is CVE-2026-86184?

CVE-2026-86184 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-86184?

Yes. A fix has been recorded for CVE-2026-86184. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-86184 affect?

CVE-2026-86184 affects Lara Dashboard < 1.3.0, laradashboard/laradashboard (self-hosted Laravel dashboards). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-86184?

Upgrade to v1.3.0; or disable screenshot-login and ensure APP_ENV=production until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Lara Dashboard < 1.3.0laradashboard/laradashboard (self-hosted Laravel dashboards)
impact

Unauthenticated GET /screenshot-login/{email} can grant valid sessions, enabling admin access, data exfiltration, and arbitrary code execution via module installer.

action required

Immediate action required

affected versions
laradashboard laradashboard
  • affected< 1.3.0
vendor says fixed in1.3.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free