CVE-2026-101678

Description

A flaw was found in MySQL Connector/J. An unauthenticated remote attacker could exploit this vulnerability across the network by enticing a user to interact with malicious requests. A successful attack allows the attacker to cause a partial Denial of Service (DoS), leading to temporary service disruption for applications using the connector.

Statement

This vulnerability is rated as Moderate severity because exploitation requires user interaction and only results in a partial denial of service without compromising system confidentiality or integrity. In Red Hat environments, MySQL Connector/J is primarily utilized as a client-side JDBC driver within Java applications and middleware to communicate with MySQL database instances. Because the issue cannot be triggered autonomously and does not allow unauthorized data access or code execution, the impact is confined to transient client availability disruptions.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.3N/A4.3
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactLowN/ALow

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.