# CVE-2025-10681: Gardyn Mobile Application and Device Firmware Use Hard-coded Credentials

> Hardcoded storage credentials in the Gardyn mobile app and firmware allow unauthorized access to production storage containers.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-wp3p-cjw9-x99v

## What is CVE-2025-10681?

CVE-2025-10681 is a high-severity vulnerability in Gardyn Cloud API, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Storage credentials are hardcoded in the mobile app and device firmware. These credentials do not adequately limit end user permissions and do not expire within a reasonable amount of time. This vulnerability may grant unauthorized access to production storage containers.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2025-10681?


## How do I fix CVE-2025-10681?

No fix has been published for CVE-2025-10681 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10681 being exploited?

There is no known exploitation of CVE-2025-10681 in the wild and no public exploit code.

Public exploit code:

- CVE-2025-10681: Hardcoded Azure Blob Storage Account Key — Gardyn Home Kit (ICSA-26-055-03) (github_poc): https://github.com/MichaelAdamGroberman/CVE-2025-10681

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10681 and fix it if it is affected.

What it is: CVE-2025-10681 is a high-severity vulnerability in Gardyn Cloud API, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10681 in the wild and no public exploit code.

Affected product: Gardyn Cloud API. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10681/ (Markdown: https://insights.sbomify.com/CVE-2025-10681/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10681
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10681
- OSV: https://osv.dev/vulnerability/CVE-2025-10681

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10681/
Summaries are generated and may contain mistakes; the official description above is the record.