CVE-2025-33012VulnerabilityPublished 7 Nov 2025

CVE-2025-33012: IBM Db2 · Use of a Key Past its Expiration Date

Affects IBM Db2Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.3Medium

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

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

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

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

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: 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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 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
Ibmibm/db2`pkg:deb/ibm/db2`Other threats	Affected =10.5.0 =11.1.0 =11.5.0 =12.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately audit and monitor IBM Db2 user accounts for signs of unusual login attempts or lockout bypass activity. 2) Enforce strict password policies including timely password changes and multi-factor authentication (MFA) to reduce reliance on password expiration alone. 3) Restrict network access to Db2 instances using firewall rules and network segmentation to limit exposure to authenticated users only. 4) Apply compensating controls such as enhanced logging and alerting on authentication events to detect anomalous behavior related to expired password usage. 5) Engage with IBM support to obtain any available patches or hotfixes as soon as they are released and plan for prompt deployment. 6) Consider temporary disabling of password reuse or expired password acceptance if configurable in Db2 settings. 7) Conduct regular security assessments and penetration tests focusing on authentication mechanisms within Db2 environments. 8) Educate administrators and users about the risks of password expiration bypass and the importance of reporting suspicious account activity. These steps go beyond generic advice by focusing on monitoring, access restriction, and compensating controls tailored to the specific vulnerability.

Description

IBM Db2 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux could allow an authenticated user to regain access after account lockout due to password use after expiration date.

Impact

For European organizations, this vulnerability could allow attackers with valid but expired credentials to regain access after account lockout, undermining account lockout policies designed to prevent brute force or unauthorized access attempts. This can lead to unauthorized data access, potential data manipulation, or disruption of database availability. Organizations in finance, healthcare, government, and critical infrastructure sectors that rely on IBM Db2 for sensitive data storage and processing are particularly at risk. The ability to bypass lockout controls could facilitate lateral movement within networks, persistence of threat actors, and complicate incident response efforts. Although the vulnerability requires authenticated access, the ease of exploitation over the network without user interaction increases the threat surface. The medium severity rating suggests that while the impact is not catastrophic, it is significant enough to warrant immediate attention to prevent escalation or combined attacks. Failure to address this vulnerability could result in regulatory compliance issues under GDPR and other European data protection laws if unauthorized access leads to data breaches.

CWE-324Use of a Key Past its Expiration Date (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.
Architecture and Design
Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2025, 18:57 UTC

WeaknessesCWE-324

Technical details

References

Community reviews

Related threats