# CVE-2026-86436: Lara Dashboard before 1.3.2 Missing Authorization in Post-Builder Media Upload Endpoints

> Authenticated users without content permissions can upload executable files to the web root, potentially leading to remote code execution if server configuration allows.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-v24q-8gmj-8457

## What is CVE-2026-86436?

CVE-2026-86436 is a medium-severity missing authorization vulnerability in laradashboard, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lara Dashboard before 1.3.2 fails to authorize access to the post-builder image and video upload endpoints, allowing authenticated accounts without content permissions to upload files. Attackers can upload polyglot files with attacker-chosen extensions to the public web root and execute code if the deployment permits execution of the uploaded file type.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-86436 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86436 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86436 is a medium-severity missing authorization vulnerability in laradashboard, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86436 exists.

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-86436/ (Markdown: https://insights.sbomify.com/CVE-2026-86436/index.md)
```

## Sources

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

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