Unauthenticated device-log disclosure via public blob storage
Published Jul 2, 2026 · Updated Jul 2, 2026
Information disclosure in Gardyn Cloud API before 2.12.2026 and device firmware before master.627 allows remote attackers to read device logs. The device-log Azure Blob container permits anonymous container listing and object reads instead of enforcing private access. No account or user interaction is required; exposed logs contain device identifiers, Wi-Fi SSIDs, internal paths, configurations, firmware versions, boot data, scheduled-task details, and errors.
Summary
What happened
Information disclosure in Gardyn Cloud API before 2.12.2026 and device firmware before master.627 allows remote attackers to read device logs. The device-log Azure Blob container permits anonymous container listing and object reads instead of enforcing private access. No account or user interaction is required; exposed logs contain device identifiers, Wi-Fi SSIDs, internal paths, configurations, firmware versions, boot data, scheduled-task details, and errors.
The record
- CVE
- CVE-2026-55726
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- Gardyn
- Product
- Gardyn Studio Firmware
- Classifications
- CWE-497, T1530
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <master.627
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo