# CVE-2026-82448: Shinobi before commit 5a76c74f Arbitrary Database Query Execution via Hardcoded Child Node Key

> Unauthenticated attackers can use a hardcoded key to execute arbitrary database queries, reading and modifying user and camera data.

- **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:** 29 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-4v5f-2v2r-748m

## What is CVE-2026-82448?

CVE-2026-82448 is a critical vulnerability in Shinobi, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Shinobi before commit 5a76c74f contains a hardcoded connection key in the child node service that allows unauthenticated attackers to execute arbitrary database queries. Attackers reaching the child node port can present the hardcoded key during WebSocket handshake, then dispatch SQL queries through the onWebSocketDataFromChildNode handler to read and modify user records and camera configuration.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-82448 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82448 is a critical vulnerability in Shinobi, published on 29 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-82448 in the wild and no public exploit code.

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

## Sources

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

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