dbcve.org
Flink CdcApplication · Apache

CVE-2025-62228

HIGH · 8.8 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache Flink CDC version 3.4.0 was vulnerable to a SQL injection via maliciously crafted identifiers eg. crafted database name or crafted table name. Even through only the logged-in database user can trigger the attack, we recommend users update Flink CDC version to 3.5.0 which address this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Flink CDC version 3.4.0 contains a SQL injection vulnerability in its handling of database and table identifiers. Attackers with valid database credentials can exploit this by submitting specially crafted database or table names that bypass input sanitization, allowing arbitrary SQL commands to be executed.

MitigationUpgrade to Apache Flink CDC version 3.5.0 which contains the fix for this SQL injection vulnerability. As a defense-in-depth measure, enforce strict input validation on all user-supplied identifiers and apply least-privilege principles to database accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Flink CdcApplication
Affected:= 3.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Apache Flink CDC version
    Run 'flink-cdc-version' or check the JAR file name in the Flink lib directory, or query the classpath for org.apache.flink:flink-cdc:3.4.0
    Affected if The installed version is exactly 3.4.0
  2. Confirm CDC pipeline is using database connectors
    Review Flink CDC job configurations or deployed JARs that connect to source databases
    Affected if CDC connectors are actively processing database and table identifiers from external sources
  3. Check for user-supplied database or table identifier inputs
    Inspect CDC connector configurations for dynamic table or database name settings, or logs showing identifier parsing
    Affected if Database or table names are being passed from user input or external sources without validation
  4. Verify database credentials are accessible to untrusted users
    Review access controls on CDC connector configurations and database accounts used by Flink CDC
    Affected if Users with only database-level credentials (not admin) can submit arbitrary identifiers to the CDC pipeline

You are affected if Apache Flink CDC version 3.4.0 is installed and CDC pipelines process database or table identifiers from external sources without additional input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apache Flink CDC version 3.5.0 which contains the fix for this SQL injection vulnerability. As a defense-in-depth measure, enforce strict input validation on all user-supplied identifiers and apply least-privilege principles to database accounts.

Recommended fix High confidence

Apache Flink CDC 3.5.0

  1. Download Apache Flink CDC version 3.5.0 from the official Apache distribution (https://flink.apache.org/downloads/)
  2. Stop the running Flink CDC 3.4.0 instance
  3. Backup your current configuration files, custom connectors, and any custom scripts
  4. Install or deploy Flink CDC 3.5.0 to your environment
  5. Restore your configuration files to the new installation
  6. Verify that your connectors and pipelines work correctly with the new version
  7. Start the Flink CDC 3.5.0 instance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flink Cdc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62228 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data