dbcve.org
WolfsshApplication

CVE-2025-11625

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to after 1.4.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Improper host authentication vulnerability in wolfSSH version 1.4.20 and earlier clients that allows authentication bypass and leaking of clients credentials.

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

wolfSSH client versions 1.4.20 and earlier contain an improper host authentication vulnerability that allows remote servers to bypass authentication checks and potentially exfiltrate client credentials. This client-side flaw could allow malicious SSH servers to impersonate legitimate servers and capture authentication data from connecting clients.

MitigationUpdate wolfSSH clients to a version beyond 1.4.20 once a patch is released. Verify all client configurations and consider rotating credentials that may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WolfsshApplication
Affected:<= 1.4.20

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

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

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. Determine wolfSSH client version
    Run 'wolfSSH -V' or check the library version in your application dependencies (e.g., libwolfssh version file, package manifest, or build info)
    Affected if Version is 1.4.20 or earlier
  2. Identify wolfSSH client usage
    Search your codebase, deployed binaries, and runtime dependencies for libwolfssh.so, libwolfssh.a, or wolfssh library imports
    Affected if wolfSSH client library is present and version is unknown or <= 1.4.20
  3. Check for host key verification implementation
    Inspect your wolfSSH client configuration code for calls to wolfSSH_SetHostKey, wolfSSH_CTX_load_host_key, or similar host key loading functions. Also check if the application verifies the known_hosts file
    Affected if Host key verification is not properly implemented or is missing in the client connection code
  4. Audit SSH client connections
    Review network logs or application logs for SSH connections established using wolfSSH client. Check if host key fingerprint validation is logged or enforced
    Affected if Connections are made without documented host key fingerprint verification

You are affected if wolfSSH client version 1.4.20 or earlier is in use AND the application performs SSH connections where host key verification can be bypassed.

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
Upgrade available Upgrade to a release after 1.4.20
Vendor patch github.com →
Interim mitigation

Update wolfSSH clients to a version beyond 1.4.20 once a patch is released. Verify all client configurations and consider rotating credentials that may have been exposed.

Recommended fix Moderate confidence

wolfSSH version after 1.4.20 (check GitHub releases for the version containing PR #840 fix)

  1. 1. Navigate to the wolfSSH GitHub repository at https://github.com/wolfSSL/wolfssh
  2. 2. Identify the fixed release version (the version containing the fix from PR #840, which should be after version 1.4.20)
  3. 3. Download the source code for the fixed version
  4. 4. Review the release notes or changelog for any migration requirements
  5. 5. Build the new version following the standard wolfSSH build process (./autogen.sh, ./configure, make, make install)
  6. 6. Ensure any applications linking against wolfSSH are rebuilt to use the new library version
  7. 7. Test thoroughly to verify the authentication vulnerability is resolved

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

Fix this in Wolfssh Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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