# CVE-2026-55726: Gardyn IoT Hub Exposure of Sensitive System Information to an Unauthorized Control Sphere

> Attackers can access sensitive device logs from the public Azure Blob Storage container without authentication, exposing system information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-pfg9-vjvh-f5rw

## What is CVE-2026-55726?

CVE-2026-55726 is a medium-severity vulnerability in Gardyn Cloud API, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Azure Blob Storage container used for Gardyn device logs is publicly listable without authentication. A malicious user would be able to access any device log file available in the blob storage container.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2026-55726 being exploited?

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

Public exploit code:

- CVE-2026-55726: Publicly Listable Azure Blob Storage Container (device logs) - Gardyn (ICSA-26-183-03) (github_poc): https://github.com/MichaelAdamGroberman/CVE-2026-55726

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55726 is a medium-severity vulnerability in Gardyn Cloud API, published on 2 Jul 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-55726 in the wild and no public exploit code.

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

## Sources

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

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