dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-10681

HIGH · 8.6 CVSS v3.1 Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
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.

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

Storage credentials are hardcoded directly into the mobile app and device firmware binaries. These embedded credentials have excessive permissions that are not scoped to individual end users and lack expiration mechanisms, allowing potential unauthorized access to production storage containers if the credentials are extracted.

MitigationReplace hardcoded credentials with dynamic, time-limited access tokens or scoped IAM credentials, implement proper credential rotation, and ensure credentials are not embedded in client-side code or firmware.

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
Low
Availability
Low

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

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. Search mobile app source code for hardcoded storage credentials
    Review all source code files in the mobile application repository, specifically looking for API keys, access tokens, storage access keys, or secret values embedded directly in code (e.g., hardcoded strings in configuration files, source files, or resource files). Use grep or similar tools to search for patterns like 'api_key', 'access_key', 'secret', 'token', 'credentials' in plaintext.
    Affected if Any hardcoded storage credentials (API keys, tokens, access keys) are found directly in the mobile application source code.
  2. Search firmware for embedded credentials
    Extract and analyze the device firmware image or binary files. Search for plaintext storage credentials, API keys, access tokens, or secret strings embedded within firmware files. Usebinwalk, strings, or firmware analysis tools to extract and inspect contents.
    Affected if Any hardcoded storage credentials are found embedded within the device firmware.
  3. Verify credential expiration policy
    Check whether the discovered hardcoded credentials have an expiration date, time-to-live (TTL), or rotation policy configured. Review credential metadata or consult the storage service documentation to determine if the credentials are set to expire or require manual rotation.
    Affected if The hardcoded credentials do not expire and have no rotation policy configured.
  4. Assess credential permission scope
    Examine the access permissions associated with the hardcoded credentials. Determine whether the credentials grant full read/write access, administrative privileges, or excessive permissions beyond what is required for the application's intended function.
    Affected if The hardcoded credentials provide excessive permissions (e.g., full administrative access, unrestricted read/write to all buckets/containers) rather than least-privilege access.
  5. Confirm absence of secrets management
    Verify whether the application uses a proper secrets management solution (environment variables, secrets manager, vault) or relies solely on hardcoded values embedded in code or firmware.
    Affected if The application uses hardcoded credentials in source code or firmware instead of a secrets management solution.

A user is affected if their mobile application source code or device firmware contains hardcoded storage credentials that provide excessive permissions without expiration and without using a secrets management solution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace hardcoded credentials with dynamic, time-limited access tokens or scoped IAM credentials, implement proper credential rotation, and ensure credentials are not embedded in client-side code or firmware.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10681 — 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-10681 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