Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/michaeladamgroberman/cve-2026-25197
ReconnaissanceIoT SecurityVulnerability AnalysisInformation GatheringWeb SecurityPrivacyPapers & ResearchLearning & EducationAPI Security

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
GitHubmichaeladamgroberman/cve-2026-25197

CVE-2026-25197

CVE-2026-25197: Authorization Bypass via IDOR — Gardyn Home Kit (ICSA-26-055-03)

View RepositoryWebsite
53 months agoNot yet reviewed

CVE-2026-25197: Authorization Bypass via User-Controlled Key (IDOR)

Advisory

FieldValue
CVECVE-2026-25197
ICSAICSA-26-055-03 (Update A)
CVSS 3.19.1 (Critical)
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CWECWE-639 (Authorization Bypass Through User-Controlled Key)
ResearcherMichael Groberman — Gr0m
Published2026-04-02 (Update A)

Product

FieldValue
VendorGardyn
ProductGardyn Home Kit 1.0, 2.0, 3.0, 4.0; Gardyn Studio 1.0, 2.0
ComponentCloud API
Affected VersionsCloud API < 2.12.2026

Summary

Two REST API endpoints return user data without per-user authorization checks:

  • /api/users returns the full user list. No authentication is required.
  • /api/user/{id} returns the profile of the user identified by {id}. No verification is performed that the requesting party is authorized to access that user's record.

User identifiers are sequential integers, allowing enumeration of all 134,215+ user accounts and their associated devices via the /api/user/{id} endpoint.

Vulnerability Details

Unauthenticated User Listing

The /api/users endpoint accepts unauthenticated requests and returns the complete user list. No authentication, rate limiting, or access logging is performed on this endpoint.

root@kitploit:~
GET [REDACTED — Cloud API host]/api/users
Authentication: NONE

User Profile Endpoint — IDOR

The /api/user/{id} endpoint accepts a user ID as a path parameter and returns the corresponding user's profile. The endpoint performs no authorization check to verify that the requesting party is associated with the requested user. User IDs are sequential integers.

root@kitploit:~
GET [REDACTED — Cloud API host]/api/user/{user_id}

Data exposed per user:

FieldDescription
NameFull name
EmailEmail address
AddressPhysical address
Devices

Predictable Camera Image URLs

Camera image URLs follow a predictable pattern incorporating the sequential user ID, device ID, and timestamp. Once user and device IDs are obtained via the IDOR, an attacker can construct valid URLs to access any user's camera images without additional authentication. The Gardyn camera captures still images only — no audio streams are recorded or exposed.

Impact

  • PII exposure for 134,215+ users via sequential enumeration
  • Access to home interior camera images from approximately 115,000 Gardyn cameras
  • Complete user-to-device mapping enabling targeted attacks
  • Two independent vectors: /api/users (no auth, full user list) and /api/user/{id} (sequential IDOR, any user's data)
  • Privacy violation at scale -- names, emails, physical addresses, device data, camera images

Azure Services Available for This Class of Endpoint

ServicePurpose
Azure AD B2CToken-based identity with per-user scoped claims
UUID/GUID IdentifiersNon-enumerable identifiers

Remediation

Gardyn recommends upgrading to Cloud API version 2.12.2026 or later. See https://mygardyn.com/security/ for additional information.

Recommended mitigations for device owners:

  • Isolate the Gardyn device on a dedicated VLAN or IoT network segment
  • Consider whether the built-in camera captures sensitive areas of your home

Recommended fix for the vendor:

  1. Implement proper authorization checks on all user and device data endpoints
  2. Replace sequential integer IDs with non-enumerable identifiers (UUIDs)
  3. Validate that the authenticated user owns the requested resource before returning data
  4. Rotate API credentials and remove from Firebase Remote Config
  5. Implement rate limiting on user/device lookup endpoints
  6. Audit access logs for enumeration patterns

Timeline

DateEvent
2025-10-14Initial disclosure to vendor
2025-12-11Disclosure to CERT/CC
2026-02-24ICSA-26-055-03 published (initial)
2026-04-02ICSA-26-055-03 Update A -- CVE-2026-25197, CVE-2026-28766, CVE-2026-32646, CVE-2026-28767, CVE-2026-32662 added

References

  • CVE-2026-25197 -- CVE Record
  • ICSA-26-055-03
  • CWE-639: Authorization Bypass Through User-Controlled Key

Credit

Reported by Michael Groberman — Gr0m to CISA.

Download Tool
Associated device IDs and serials
SettingsAccount configuration
Authorization MiddlewarePer-request authorization verification