Quick answers
- Is CVE-2026-25197 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25197 being exploited in the wild.
- How severe is CVE-2026-25197?
- Critical severity, with a CVSS score of 9.1, published 3 April 2026.
- Which products and versions are affected?
- Gardyn Cloud API < 2.12.2026.
- Is there a fix for CVE-2026-25197?
- A patch was published on 2026-02-24: Original vendor remediation date Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25197 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-25197?
- Check whether you run Gardyn Cloud API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Gardyn Cloud API is vulnerable to an Authorization Bypass Through User-Controlled Key (CWE-639), commonly known as Insecure Direct Object Reference (IDOR). A specific API endpoint fails to properly validate that the authenticated user has permission to access the requested resource ID. By modifying the 'id' number in an API call, a remote attacker can pivot to other user profiles. This can lead to the exposure of sensitive demographic information (names, addresses, phone numbers), access to plant photos, and potential remote control of Gardyn Home and Studio devices. The vulnerability is fixed in Cloud API version 2.12.2026, which corresponds with Gardyn Mobile App version 2.11.0 and device firmware version 627.
Affected products
- Gardyn Cloud API < 2.12.2026
Timeline
- 2026-02-24: patched: Original vendor remediation date
- 2026-04-03: disclosed: Initial NVD publication
- 2026-07-02: advisory: Latest revision of CISA/ICS-CERT advisory