How severe is CVE-2025-62228?

No CVSS score has been assigned to CVE-2025-62228 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-62228?

CVE-2025-62228 affects the following packages: org.apache.flink:flink-cdc-pipeline-connectors (Maven), org.apache.flink:flink-connector-oracle-cdc (Maven), org.apache.flink:flink-connector-db2-cdc (Maven), org.apache.flink:flink-connector-sqlserver-cdc (Maven), org.apache.flink:flink-connector-mysql-cdc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-62228?

Update org.apache.flink:flink-cdc-pipeline-connectors to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62228 is resolved across your whole dependency graph.

How do I detect CVE-2025-62228 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.flink:flink-cdc-pipeline-connectors, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-62228 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2025-62228 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-62228 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-62228?

CVE-2025-62228 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-62228?

CVE-2025-62228 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-62228 published, and has it been updated?

CVE-2025-62228 was published on October 9, 2025 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-62228 — flink-cdc-pipeline-connec…

Fix: apache/flink-cdc#4123

CVE-2025-62228 is a SQL Injection vulnerability in org.apache.flink:flink-cdc-pipeline-connectors. A fix is available for org.apache.flink:flink-cdc-pipeline-connectors — see the affected versions and patch details below.

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

Published

Oct 9, 2025

Updated

Nov 5, 2025

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-62228.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

☕org.apache.flink:flink-cdc-pipeline-connectors☕org.apache.flink:flink-connector-oracle-cdc☕org.apache.flink:flink-connector-db2-cdc☕org.apache.flink:flink-connector-sqlserver-cdc☕org.apache.flink:flink-connector-mysql-cdc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.flink:flink-cdc-pipeline-connectors`	≥ 3.0.0&&< 3.5.0	3.5.0`org.apache.flink:flink-cdc-pipeline-connectors:3.5.0`
☕Maven	`org.apache.flink:flink-connector-oracle-cdc`	≥ 3.0.0&&< 3.5.0	3.5.0`org.apache.flink:flink-connector-oracle-cdc:3.5.0`
☕Maven	`org.apache.flink:flink-connector-db2-cdc`	≥ 3.0.0&&< 3.5.0	3.5.0`org.apache.flink:flink-connector-db2-cdc:3.5.0`
☕Maven	`org.apache.flink:flink-connector-sqlserver-cdc`	≥ 3.0.0&&< 3.5.0	3.5.0`org.apache.flink:flink-connector-sqlserver-cdc:3.5.0`
☕Maven	`org.apache.flink:flink-connector-mysql-cdc`	≥ 3.0.0&&< 3.5.0	3.5.0`org.apache.flink:flink-connector-mysql-cdc:3.5.0`

Affected Products

1 product · 1 configurations

Application

flink cdcapache

1 version

3.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.flink:flink-cdc-pipeline-connectors, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.flink:flink-cdc-pipeline-connectors to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62228 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-62228 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works