CVE-2026-82448
Hardcoded child-node key allows unauthenticated SQL query execution in Shinobi.
Is CVE-2026-82448 being exploited?
Not confirmed. CVE-2026-82448 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-82448?
CVE-2026-82448 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82448?
Yes. A fix has been recorded for CVE-2026-82448. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82448 affect?
CVE-2026-82448 affects Shinobi (pre-commit 5a76c74f), Shinobi childNode service, Shinobi WebSocket child-node port. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82448?
Apply commit 5a76c74f or upgraded release; restrict/block child-node port and audit DB/user changes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can present a hardcoded WebSocket key to execute arbitrary SQL, read/modify user records and camera configuration.
Immediate action required
- affected< 5a76c74f3977661ff3f9fd55a260db352c0b19c0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.