dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-26788

HIGH · 8.4 CVSS v3.1 Published 2025-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable 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
StrongKey FIDO Server before 4.15.1 treats a non-discoverable (namedcredential) flow as a discoverable transaction.

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 confidence

StrongKey FIDO Server before version 4.15.1 incorrectly processes the authentication flow for non-discoverable (named credentials), treating them as discoverable credentials. This is a logic error in the FIDO authentication protocol implementation where the server mishandles credential discovery during authentication, potentially leading to improper authentication behavior.

MitigationUpgrade StrongKey FIDO Server to version 4.15.1 or later to obtain the corrected credential flow handling.

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/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. Identify StrongKey FIDO Server installation
    Locate the StrongKey FIDO Server installation directory and check for version indicators such as a VERSION file, build properties, or check the WAR/jar file version metadata. Common locations include /opt/strongkey or the application deployment directory.
    Affected if The software is StrongKey FIDO Server and the version is identified as earlier than 4.15.1
  2. Determine installed version number
    Review version information from the application startup logs, the strongkey.properties file, or the version manifest within the deployed application artifacts. Compare the found version against the affected range.
    Affected if The installed version is any release prior to 4.15.1 (e.g., 4.14.x, 4.13.x, earlier)
  3. Verify FIDO2 authentication is enabled
    Inspect the StrongKey FIDO Server configuration files (typically strongkey.properties or fido2-config.xml) to confirm that FIDO2 authentication flows are enabled and the server is acting as a FIDO2 relying party.
    Affected if FIDO2 authentication is configured and active on the server
  4. Check for non-discoverable credential usage
    Review authentication transaction logs or policy configuration to determine whether non-discoverable (also called 'named' or 'resident key excluded') credentials are being used or allowed in authentication flows.
    Affected if Non-discoverable credential authentication paths are in use or permitted on the server
  5. Inspect authentication flow handling
    Examine the server logs during FIDO2 authentication attempts, particularly for non-discoverable credential authentications, to observe if the server treats them as discoverable credential transactions (which would indicate the vulnerability).
    Affected if Authentication logs show non-discoverable credentials being processed through discoverable credential paths, suggesting the logic error is present

The environment is affected if StrongKey FIDO Server is installed with a version prior to 4.15.1 and FIDO2 authentication with non-discoverable credentials is enabled or in use.

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

Upgrade StrongKey FIDO Server to version 4.15.1 or later to obtain the corrected credential flow handling.

Recommended fix Moderate confidence

4.15.1

  1. Download StrongKey FIDO Server version 4.15.1 from the official vendor repository
  2. Stop the StrongKey FIDO Server service
  3. Backup the existing configuration and data directories
  4. Install version 4.15.1 following the standard upgrade procedure
  5. Verify the installation by reviewing server logs
  6. Restart the StrongKey FIDO Server service
Caveat Review release notes for any configuration changes between your current version and 4.15.1

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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