CVE-2026-27073
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 · uneditedUse of Hard-coded Credentials vulnerability in Addi Addi – Cuotas que se adaptan a ti buy-now-pay-later-addi allows Password Recovery Exploitation.This issue affects Addi – Cuotas que se adaptan a ti: from n/a through <= 2.0.4.
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 · moderate confidenceHardcoded credentials embedded in the Addi mobile application (version <= 2.0.4) allow attackers to exploit the password recovery mechanism. The application contains static credentials that cannot be changed by administrators, enabling unauthorized access to user accounts through the password reset flow.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Addi mobile application versionCheck the app version on the mobile device through the app store listing, device settings (Apps > Addi > Version), or by inspecting the APK/IPA file metadataAffected if The installed version is 2.0.4 or any earlier version (versions numbered lower than or equal to 2.0.4)
-
Verify password recovery mechanism is enabledCheck if the password reset or account recovery feature is accessible in the Addi mobile application login screen or settings menuAffected if Password recovery is available and active in the application
-
Inspect application binary for hardcoded credential stringsDecompile the APK (Android) or IPA (iOS) and search within the binary or source code for static strings matching patterns like API keys, passwords, secrets, or credentials used in authentication flows. Look for hardcoded values in password reset or recovery-related code filesAffected if Hardcoded credential strings are found embedded in the application code or binary
-
Confirm credentials are static and non-editableReview the application configuration or administrative settings to verify whether the credentials used in the password recovery flow can be modified by an administrator. Check if the credentials are defined in a config file or hardcoded in source code rather than retrieved from a secure vaultAffected if Credentials are defined in static code or config files and cannot be changed through admin controls
If the Addi mobile application version is 2.0.4 or lower AND the password recovery feature is enabled, the environment contains the hardcoded credentials vulnerability described in this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace all hardcoded credentials with secure secrets management (environment variables, vault solutions), audit and remediate the password recovery flow to ensure it does not rely on static credentials, and rotate any exposed credentials immediately.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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