What is CVE-2025-62228?

CVE-2025-62228 is a medium-severity SQL injection vulnerability in org.apache.flink:flink-cdc-pipeline-connectors (maven), affecting versions >= 3.0.0, < 3.5.0. It is fixed in 3.5.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

Which packages are affected by CVE-2025-62228?

org.apache.flink:flink-cdc-pipeline-connectors (maven) versions >= 3.0.0, = 3.0.0, = 3.0.0, = 3.0.0, = 3.0.0, < 3.5.0.

Is there a fix for CVE-2025-62228?

Yes. CVE-2025-62228 is fixed in 3.5.0. Upgrade to this version or later.

Is CVE-2025-62228 exploitable, and should I be worried?

Whether CVE-2025-62228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-62228 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-62228

Q: Which packages are affected by CVE-2025-62228?

org.apache.flink:flink-cdc-pipeline-connectors (maven) versions >= 3.0.0, = 3.0.0, = 3.0.0, = 3.0.0, = 3.0.0, < 3.5.0.

Q: Is there a fix for CVE-2025-62228?

Yes. CVE-2025-62228 is fixed in 3.5.0. Upgrade to this version or later.

Q: Is CVE-2025-62228 exploitable, and should I be worried?

Whether CVE-2025-62228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-62228 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-62228?

Upgrade: org.apache.flink:flink-cdc-pipeline-connectors to 3.5.0 or later, org.apache.flink:flink-connector-oracle-cdc to 3.5.0 or later, org.apache.flink:flink-connector-db2-cdc to 3.5.0 or later, org.apache.flink:flink-connector-sqlserver-cdc to 3.5.0 or later, org.apache.flink:flink-connector-mysql-cdc to 3.5.0 or later.

Summary

Apache Flink CDC is vulnerable to SQL Injection through maliciously crafted identifiers

Apache Flink CDC version 3.0.0 to before 3.5.0 are 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, users are recommended to update Flink CDC version to 3.5.0 which address this issue.

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Affected versions

org.apache.flink:flink-cdc-pipeline-connectors (>= 3.0.0, < 3.5.0) org.apache.flink:flink-connector-oracle-cdc (>= 3.0.0, < 3.5.0) org.apache.flink:flink-connector-db2-cdc (>= 3.0.0, < 3.5.0) org.apache.flink:flink-connector-sqlserver-cdc (>= 3.0.0, < 3.5.0) org.apache.flink:flink-connector-mysql-cdc (>= 3.0.0, < 3.5.0)

Security releases

org.apache.flink:flink-cdc-pipeline-connectors → 3.5.0 (maven) org.apache.flink:flink-connector-oracle-cdc → 3.5.0 (maven) org.apache.flink:flink-connector-db2-cdc → 3.5.0 (maven) org.apache.flink:flink-connector-sqlserver-cdc → 3.5.0 (maven) org.apache.flink:flink-connector-mysql-cdc → 3.5.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.flink:flink-cdc-pipeline-connectors to 3.5.0 or later; org.apache.flink:flink-connector-oracle-cdc to 3.5.0 or later; org.apache.flink:flink-connector-db2-cdc to 3.5.0 or later; org.apache.flink:flink-connector-sqlserver-cdc to 3.5.0 or later; org.apache.flink:flink-connector-mysql-cdc to 3.5.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-62228? CVE-2025-62228 is a medium-severity SQL injection vulnerability in org.apache.flink:flink-cdc-pipeline-connectors (maven), affecting versions >= 3.0.0, < 3.5.0. It is fixed in 3.5.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
Which packages are affected by CVE-2025-62228?
- org.apache.flink:flink-cdc-pipeline-connectors (maven) (versions >= 3.0.0, < 3.5.0)
- org.apache.flink:flink-connector-oracle-cdc (maven) (versions >= 3.0.0, < 3.5.0)
- org.apache.flink:flink-connector-db2-cdc (maven) (versions >= 3.0.0, < 3.5.0)
- org.apache.flink:flink-connector-sqlserver-cdc (maven) (versions >= 3.0.0, < 3.5.0)
- org.apache.flink:flink-connector-mysql-cdc (maven) (versions >= 3.0.0, < 3.5.0)
Is there a fix for CVE-2025-62228? Yes. CVE-2025-62228 is fixed in 3.5.0. Upgrade to this version or later.
Is CVE-2025-62228 exploitable, and should I be worried? Whether CVE-2025-62228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-62228 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-62228?
- Upgrade org.apache.flink:flink-cdc-pipeline-connectors to 3.5.0 or later
- Upgrade org.apache.flink:flink-connector-oracle-cdc to 3.5.0 or later
- Upgrade org.apache.flink:flink-connector-db2-cdc to 3.5.0 or later
- Upgrade org.apache.flink:flink-connector-sqlserver-cdc to 3.5.0 or later
- Upgrade org.apache.flink:flink-connector-mysql-cdc to 3.5.0 or later