Critical

IDOR in Gardyn Cloud API user profile endpoint

IdentifiersCVE-2026-25197CWE-639· Authorization Bypass Through…

CVE-2026-25197 is an authorization flaw in Gardyn Cloud API versions prior to 2.12.2026. According to the provided description, a specific API endpoint allows a user to access or pivot to other user profiles by modifying the numeric ID value in the request. This is consistent with an insecure direct object reference / user-controlled key weakness in which the server fails to enforce object-level authorization on the referenced profile resource.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthorized access to other users' profile data and unauthorized interaction with profile-associated resources by changing the target identifier in API requests. Based on the provided CVSS metadata, the primary impacts are high confidentiality and high integrity impact, with no stated availability impact. In practical terms, an attacker could enumerate or access other users' profiles and potentially alter profile-related data or actions exposed through the vulnerable endpoint.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict exposure of the affected API, monitor for anomalous requests that iterate or manipulate profile ID values, and add compensating controls such as API gateway authorization enforcement and logging for cross-account access attempts. Review application logic for other endpoints that rely on client-supplied identifiers and validate authorization on every object access.

Remediation

Patch, then assume compromise.

Upgrade Gardyn Cloud API to version 2.12.2026 or later, as the issue affects versions prior to 2.12.2026. The vulnerable endpoint should enforce server-side object-level authorization checks so that the authenticated principal can only access resources they are explicitly permitted to access. Numeric or otherwise user-supplied object identifiers should never be trusted as proof of authorization.

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 4 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 4 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

MygardynCloud Apiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

10 SOURCESView more in app

cyber security newsNews

Apr 21, 2026

Critical Gardyn Smart Gardens Vulnerabilities Let Attackers Control Devices Remotely

A recently added vulnerability affecting Gardyn Cloud API versions prior to 2.12.2026 as part of a broader set of critical flaws in the Gardyn ecosystem.

cvefeed high severityNews

Apr 3, 2026

CVE-2026-25197 - Gardyn Cloud API Authorization Bypass Through User-Controlled Key

An access control vulnerability in which a specific endpoint allows users to access other user profiles by modifying the ID number in an API call.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8