CVE-2025-10681
Hardcoded storage credentials in mobile app/firmware allow unauthorized storage access.
Is CVE-2025-10681 being exploited?
Not confirmed. CVE-2025-10681 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2025-10681?
CVE-2025-10681 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-10681?
Not known from our data. No patch reference has been recorded for CVE-2025-10681, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-10681 affect?
CVE-2025-10681 affects Mobile app, Device firmware, Production storage containers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-10681?
Remove hardcoded creds; implement proper auth; rotate keys; deploy update
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Hardcoded credentials allow access to production storage containers, enabling read/write and potential breach.
Patch when possible
- affected< 2.12.2026
- affected< 2.11.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.