Skip to content
IoT

CVE-2026-13768

9.5
Critical
EPSS 0.65%Jul 3, 2026

Privileged iothubowner key exposed enabling device control and network pivot.

common questions

Is CVE-2026-13768 being exploited?

Not confirmed. CVE-2026-13768 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.65% probability of exploitation in the next 30 days.

How severe is CVE-2026-13768?

CVE-2026-13768 is rated Critical with a CVSS score of 9.5. 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-13768?

Not known from our data. No patch reference has been recorded for CVE-2026-13768, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-13768 affect?

CVE-2026-13768 affects Gardyn IoT devices, Gardyn Home Kit, Gardyn Studio. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-13768?

Apply vendor patch when available; rotate keys; isolate devices; monitor activity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Gardyn IoT devicesGardyn Home KitGardyn Studio
impact

Key lets attacker view all device connections, run commands on a device, and pivot to other devices on the network.

action required

Patch when possible

affected versions
Gardyn Gardyn Cloud API
  • affected< 2.12.2026
Gardyn Gardyn Home Firmware
  • affected< master.627
Gardyn Gardyn Studio Firmware
  • affected< master.627

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free