dbcve.org
CWE-1188Weakness · CWE-1188

CVE-2026-39920

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
BridgeHead FileStore versions prior to 24A (released in early 2024) expose the Apache Axis2 administration module on network-accessible endpoints with default credentials that allows unauthenticated remote attackers to execute arbitrary OS commands. Attackers can authenticate to the admin console using default credentials, upload a malicious Java archive as a web service, and execute arbitrary commands on the host via SOAP requests to the deployed service.

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

BridgeHead FileStore versions before 24A expose the Apache Axis2 administration console on network-accessible endpoints with default credentials, enabling unauthenticated attackers to upload malicious Java archives and execute arbitrary OS commands via SOAP requests.

MitigationUpgrade to BridgeHead FileStore version 24A or later. If immediate upgrade is not feasible, change default Axis2 credentials and restrict network access to the admin console.

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
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. Identify BridgeHead FileStore installation
    Locate BridgeHead FileStore installation directory and check version information in release notes, about dialog, or version file. Common paths: /opt/bridgehead/filestore, C:\Program Files\BridgeHead\FileStore, or check installed packages list.
    Affected if Version is found to be before 24A (e.g., 23B, 23A, older)
  2. Verify Axis2 admin console endpoint is exposed
    Attempt to access the Axis2 administration console over the network using HTTP/HTTPS. Common endpoints: http://hostname/axis2/axis2-admin, http://hostname/axis2-admin/, or /services/axis2. Use curl or a browser from an external host.
    Affected if The Axis2 admin console is accessible from a network-accessible endpoint (not localhost-only)
  3. Test default Axis2 credentials
    Attempt to log in to the Axis2 admin console with default credentials. Common defaults: username 'axis2' with password 'axis2', or 'admin' with password 'axis2'. Submit login via the web form or check response headers.
    Affected if Default credentials (axis2/axis2 or admin/axis2) successfully authenticate to the Axis2 admin console
  4. Confirm SOAP service endpoint accessibility
    Check if Axis2 SOAP services are reachable over the network. Try accessing http://hostname/axis2/services/ or similar service endpoints. These are required for the arbitrary command execution aspect of the vulnerability.
    Affected if Axis2 SOAP service endpoints are accessible from the network

The environment is affected if BridgeHead FileStore version is before 24A AND the Axis2 admin console is network-accessible with default credentials still enabled.

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 to BridgeHead FileStore version 24A or later. If immediate upgrade is not feasible, change default Axis2 credentials and restrict network access to the admin console.

Recommended fix Moderate confidence

BridgeHead FileStore 24A

  1. Upgrade BridgeHead FileStore to version 24A (released in early 2024) or later to resolve the insecure default credential vulnerability.
  2. If immediate upgrade is not possible, disable or restrict network access to the Apache Axis2 administration module endpoints.
  3. If the Axis2 admin module must remain accessible, change the default credentials immediately according to Axis2 documentation.
  4. Implement network segmentation to limit exposure of administrative interfaces to untrusted networks.
  5. Review and audit all deployed web services for any unauthorized deployments following any suspected compromise.
Caveat Review release notes for 24A to check for any configuration or integration changes that may require adjustments during upgrade.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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