IBM Db2 Mirror for i is vulnerable to Cross-Site Request Forgery []

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/Db2 Mirror for i (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/Db2 Mirror for i.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 14, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 14, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 14, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• Concrete CMS 9.0.0 to 9.5.2 is vulnerable to CSRF on Orphan Block CleanupAlso CWE-352
• Langflow is vulnerable to authentication bypass and insufficient session expirationSame generic ecosystem
• Langflow OSS is affected by server-side request forgery due to missing URL validation in flow componentsSame generic ecosystem
• Langflow is vulnerable to Server-Side Request Forgery due to missing or bypassable URL validation in multiple componentsSame generic ecosystem
• Langflow is vulnerable to server-side request forgery due to missing egress validation on server-side URL fetchesSame generic ecosystem
• Multiple secuirty vulnerabilies addressed with IBM Business Automation Workflow August 2026Same generic ecosystem