dbcve.org
Bsafe Crypto JApplication · Dell

CVE-2025-26333

HIGH · 7.5 CVSS v3.1 Published 2025-09-25
Fix available
A fix is available. Upgrade to 6.3.1 or later.
See remediation →
84/100
Remediation priority · High
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
Dell BSAFE Crypto-J generates an error message that includes sensitive information about its environment and associated data. A remote attacker could potentially exploit this vulnerability, leading to information exposure.

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 · low confidence

Dell BSAFE Crypto-J library contains a vulnerability where error messages expose sensitive environment information (system paths, configuration details, or crypto-related data) to remote attackers, potentially aiding further exploitation.

MitigationReview and sanitize all error message paths in the library to remove sensitive environment details, replacing with generic error messages that don't reveal system-specific information.

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
Bsafe Crypto JApplication
Affected:>= 6.0, < 6.3.1= 7.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify BSAFE Crypto-J library file
    Locate the bsafecrypto*.jar file in your application or system. Check the META-INF/MANIFEST.MF inside the JAR for the Implementation-Version attribute, or check your dependency management system (Maven pom.xml, Gradle build.gradle) for the bsafecrypto-j library version declaration.
    Affected if The declared version matches 6.0 through 6.3.0, or exactly 7.0
  2. Verify library version from classpath
    Run: jar tf bsafecrypto*.jar | grep META-INF/MANIFEST, then inspect the manifest file. Or use: java -cp bsafecrypto*.jar java.lang.System.getProperty("bsafe.version") if such a property exists, or check documentation for version retrieval method.
    Affected if Version returned is within 6.0-6.3.0 range or equals 7.0
  3. Review application dependency declarations
    Search project configuration files (pom.xml, build.gradle, package.json, or similar) for bsafecrypto-j or dell-bsafe dependencies. Note the declared version number.
    Affected if Dependency specifies version 6.0.x, 6.1.x, 6.2.x, 6.3.0, or 7.0.x
  4. Inspect runtime error message behavior
    Trigger library operations that produce error conditions (such as invalid crypto operations or configuration errors). Capture and examine the error messages returned by the library.
    Affected if Error messages contain system file paths, environment variable values, internal configuration details, or crypto key material that should not be exposed.

You are affected if the installed BSAFE Crypto-J library version is 6.0.x, 6.1.x, 6.2.x, 6.3.0, or exactly 7.0, and your application displays error messages that reveal system paths, configuration details, or sensitive crypto-related data.

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 6.3.1 or later
Fixed in 6.3.1
Interim mitigation

Review and sanitize all error message paths in the library to remove sensitive environment details, replacing with generic error messages that don't reveal system-specific information.

Recommended fix Moderate confidence

6.3.1 or later (6.x line); contact Dell for specific fixed version beyond 7.0

  1. 1. Identify the current version of Dell BSAFE Crypto-J in your environment
  2. 2. Contact Dell customer support or consult the Dell BSAFE product documentation to confirm the exact fixed release for version 7.x
  3. 3. Upgrade to Dell BSAFE Crypto-J version 6.3.1 or later (for the 6.x line)
  4. 4. If using version 7.0, upgrade to the fixed release beyond 7.0 as specified by Dell
  5. 5. After upgrading, verify that error messages no longer expose sensitive environment or configuration information
  6. 6. Test the updated library in a non-production environment before deploying to production
Caveat Review Dell release notes for any API changes or deprecations between your current version and the target version

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

Fix this in Bsafe Crypto J Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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