CVE-2025-33081VulnerabilityPublished 3 Feb 2026Updated 5 Feb 2026

CVE-2025-33081: IBM Concert · Cleartext Storage of Sensitive Information

Affects IBM ConcertSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.3Low

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 3 Feb 2026
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
IBMConcert	Affected >=1.0.0 <=2.1.0	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:concert:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:concert:2.1.0:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-33081, European organizations should implement the following specific measures: 1) Restrict local user access to systems running IBM Concert to only trusted personnel and enforce strict user account management policies. 2) Review and harden file system permissions on log directories to prevent unauthorized read access by non-privileged users. 3) Implement encryption or secure storage mechanisms for log files containing sensitive information, either through IBM Concert configuration if available or via external tools. 4) Regularly audit and monitor access to log files to detect unauthorized access attempts. 5) Where possible, upgrade IBM Concert to versions beyond 2.1.0 if patches addressing this issue become available. 6) Educate system administrators and users about the risks of local data exposure and enforce policies to minimize sensitive data logging. 7) Consider isolating systems running IBM Concert in secure network segments to limit local access. 8) Use host-based intrusion detection systems to alert on suspicious file access patterns related to log files. These steps go beyond generic advice by focusing on local access control, log file protection, and monitoring tailored to the nature of this vulnerability.

Description

IBM Concert 1.0.0 through 2.1.0 stores potentially sensitive information in log files that could be read by a local user.

Impact

For European organizations, the primary impact of CVE-2025-33081 is the potential unauthorized disclosure of sensitive information due to cleartext storage in log files accessible by local users. This can lead to confidentiality breaches, which may have regulatory implications under GDPR if personal or sensitive data is exposed. Although the vulnerability does not affect system integrity or availability, the exposure of sensitive information could facilitate further attacks or insider threats. Organizations with shared workstations, weak local user account management, or insufficient log access controls are at higher risk. The impact is more pronounced in sectors handling sensitive or regulated data, such as finance, healthcare, and government. Since no remote exploitation is possible, the threat is limited to insiders or attackers with physical or local network access. However, the presence of sensitive data in logs could also aid attackers in lateral movement or privilege escalation if combined with other vulnerabilities or poor security hygiene.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7257565 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 11 Feb 2026, 11:33 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats