Unauthenticated data exposure via active debug endpoints
Published Apr 3, 2026 · Updated Apr 3, 2026
Active debug code in Gardyn Cloud API before 2.12.2026 allows remote attackers to read sensitive data through exposed API endpoints. Development and test routes mirror production requests, and the development API historically returned production IoT Hub credentials without authentication. Network access alone reaches the flaw, but the published assessment limits this CVE to confidentiality impact without reported data modification or service interruption.
Summary
What happened
Active debug code in Gardyn Cloud API before 2.12.2026 allows remote attackers to read sensitive data through exposed API endpoints. Development and test routes mirror production requests, and the development API historically returned production IoT Hub credentials without authentication. Network access alone reaches the flaw, but the published assessment limits this CVE to confidentiality impact without reported data modification or service interruption.
The record
- CVE
- CVE-2026-32662
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- Gardyn
- Product
- Gardyn Cloud API
- Classifications
- CWE-489, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 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 <2.12.2026
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.
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