CVE-2025-26333VulnerabilityPublished 25 Sep 2025Updated 24 Oct 2025

CVE-2025-26333: Dell BSAFE Crypto-J · Generation of Error Message Containing Sensitive Information

Affects Dell BSAFE Crypto-JSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Dell BSAFE Crypto-J	Affected =6.0	Fixed in–

AI-suggested

To mitigate CVE-2025-26333, organizations should implement several specific measures beyond generic advice: 1) Configure Dell BSAFE Crypto-J or the hosting environment to suppress detailed error messages or redirect them to secure logs inaccessible to unauthorized users. 2) Employ network segmentation and strict access controls to limit exposure of systems running BSAFE Crypto-J to trusted networks only. 3) Monitor logs and network traffic for unusual error message patterns or reconnaissance attempts that may indicate exploitation efforts. 4) Engage with Dell support channels to obtain information on forthcoming patches or workarounds and plan timely deployment once available. 5) Conduct internal code reviews or penetration tests focusing on error handling and information leakage in cryptographic components. 6) Educate developers and system administrators on secure error handling practices to prevent similar issues. 7) Where feasible, consider temporary replacement or isolation of vulnerable components until a patch is released. These targeted actions will reduce the risk of information exposure and strengthen overall cryptographic security.

Description

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.

Impact

For European organizations, the primary impact of CVE-2025-26333 is the potential exposure of sensitive cryptographic environment information, which could aid attackers in crafting more effective attacks against cryptographic keys or systems. This exposure threatens confidentiality but does not affect data integrity or system availability. Sectors that rely heavily on cryptographic security, such as financial services, government agencies, telecommunications, and critical infrastructure operators, are particularly at risk. The vulnerability could facilitate reconnaissance activities by attackers, increasing the likelihood of subsequent exploitation attempts. Although the attack complexity is high and no exploits are currently known, the presence of this vulnerability increases the attack surface and may attract adversaries seeking to exploit cryptographic weaknesses. The lack of patches means organizations must rely on compensating controls until a fix is available. Failure to address this vulnerability could lead to data breaches or compromise of cryptographic keys, undermining trust and compliance with data protection regulations such as GDPR.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

dell.com/support/kbdoc/en-us/000296144/dsa-2025-100-dell-bsafe-crypto-j-security-update (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2025, 14:29 UTC

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats