# CVE-2026-109564: LearnHouse before 1.4.0 Missing Authorization via Playground Duplicate Endpoint

> Authenticated instructors can duplicate restricted or unpublished playgrounds, exposing private content and republishing it publicly.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 12 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-gcg2-9m45-j9r6

## What is CVE-2026-109564?

CVE-2026-109564 is a low-severity missing authorization vulnerability in LearnHouse, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LearnHouse before 1.4.0 contains a missing authorization vulnerability in POST /api/v1/playgrounds/{uuid}/duplicate that skips the read-access and draft checks enforced by get_playground. Authenticated users with playground creation rights, such as Instructors, who know a RESTRICTED or unpublished playground UUID can copy its html_content and republish it publicly.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109564 is a low-severity missing authorization vulnerability in LearnHouse, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109564 in the wild and no public exploit code.

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

## Sources

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

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