# CVE-2026-82919: cu silicon edit Endpoint views.py create_app missing authentication

> Remote attackers can access the create_app endpoint without authentication due to missing authorization checks in cu silicon.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-8cxr-fv53-crrv

## What is CVE-2026-82919?

CVE-2026-82919 is a medium-severity missing authorization vulnerability in cu silicon, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in cu silicon up to 0.1.5. Affected by this vulnerability is the function create_app of the file views.py of the component edit Endpoint. Such manipulation leads to missing authentication. The attack may be performed from remote. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-82919 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82919 is a medium-severity missing authorization vulnerability in cu silicon, published on 31 Aug 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-82919 in the wild and no public exploit code.

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

## Sources

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

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