# CVE-2026-86184: Lara Dashboard before 1.3.0 Missing Authentication in screenshot-login Route

> Unauthenticated attackers can bypass authentication in Lara Dashboard when not in production mode, gaining admin access and executing arbitrary code.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-f9pj-h2mm-qw99, GHSA-wj35-4h53-phfp

## What is CVE-2026-86184?

CVE-2026-86184 is a critical authentication bypass vulnerability in laradashboard, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lara Dashboard before 1.3.0 contains an authentication bypass vulnerability in the screenshot-login route that allows unauthenticated attackers to authenticate as any user by email when APP_ENV is not production. Attackers can request the GET /screenshot-login/{email} endpoint with a registered email address to receive a fully authenticated session, enabling access to user administration, settings, database contents, and arbitrary code execution through the module installer.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-86184?


## How do I fix CVE-2026-86184?

No fix has been published for CVE-2026-86184 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86184 being exploited?

There is no known exploitation of CVE-2026-86184 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86184 and fix it if it is affected.

What it is: CVE-2026-86184 is a critical authentication bypass vulnerability in laradashboard, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86184 in the wild and no public exploit code.

Affected product: laradashboard. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86184/ (Markdown: https://insights.sbomify.com/CVE-2026-86184/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86184
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86184
- OSV: https://osv.dev/vulnerability/CVE-2026-86184

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86184/
Summaries are generated and may contain mistakes; the official description above is the record.