dbcve.org
CWE-1392Weakness · CWE-1392

CVE-2025-29629

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Gardyn Home Kit firmware before master.619, Home Kit Mobile Application before 2.11.0, and Home Kit Cloud API before 2.12.2026 use weak default credentials for secure shell access. This may result in attackers gaining access to exposed Gardyn Home Kits.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Gardyn Home Kit firmware, mobile application, and cloud API versions prior to master.619, 2.11.0, and 2.12.2026 respectively contain weak default SSH credentials, allowing remote attackers to gain shell access to exposed devices.

MitigationUpdate all Gardyn components to the fixed versions (firmware master.619+, mobile app 2.11.0+, cloud API 2.12.2026+) and immediately change default credentials to strong, unique passwords.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify SSH is enabled and accessible on the Gardyn device
    Scan the device IP or hostname on TCP port 22 (or check device network exposure). Run: nmap -p 22 <device-ip> or nc -zv <device-ip> 22
    Affected if SSH port 22 is open and reachable on the Gardyn device, exposing it to network-based attacks
  2. Check the installed firmware version
    Log into the Gardyn device web interface or check device settings. If SSH is accessible, run: cat /etc/version or look at the SSH banner for the firmware build identifier
    Affected if Firmware version is below master.619 (e.g., earlier builds or unnumbered versions)
  3. Check the mobile application version
    Open the Gardyn mobile app, navigate to Settings > About, or check the app version in your device's app store listing or installed apps menu
    Affected if Mobile app version is below 2.11.0
  4. Identify the cloud API version in use
    Inspect network traffic from the Gardyn device or mobile app, or check API response headers/endpoints. Alternatively, check the device's connected status which may display API version in diagnostics
    Affected if Cloud API version is below 2.12.2026
  5. Test for weak default SSH credentials
    Attempt SSH login with common default credentials (check Gardyn documentation for factory defaults). Run: ssh root@<device-ip> with common default passwords such as admin, gardyn, password, or the device serial number
    Affected if SSH login succeeds using default or weak factory-set credentials

You are affected if SSH is exposed and any component (firmware, mobile app, or cloud API) is below the fixed versions while using default credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update all Gardyn components to the fixed versions (firmware master.619+, mobile app 2.11.0+, cloud API 2.12.2026+) and immediately change default credentials to strong, unique passwords.

Recommended fix Moderate confidence

Firmware: master.619 or later; Mobile Application: 2.11.0 or later; Cloud API: 2.12.2026 or later

  1. 1. Identify all affected Gardyn Home Kit devices on the network
  2. 2. For Gardyn Home Kit firmware: upgrade to version master.619 or later
  3. 3. For Home Kit Mobile Application: upgrade to version 2.11.0 or later from the app store
  4. 4. For Home Kit Cloud API: upgrade to version 2.12.2026 or later
  5. 5. Immediately change all default credentials for SSH access on affected devices
  6. 6. If SSH is not required, disable SSH access entirely
  7. 7. Implement key-based authentication instead of password-based authentication for SSH
  8. 8. Verify that all credentials have been changed and the default credentials no longer work

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29629 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data