CVE-2026-71084

Description

A flaw was found in mysql-connector-odbc. An unauthenticated attacker with local logon access to the infrastructure where MySQL Connectors executes can exploit this vulnerability. This can lead to a complete denial of service (DoS) by causing the component to crash repeatedly. Additionally, the attacker may gain unauthorized read access to a subset of data accessible by MySQL Connectors.

Statement

This Moderate severity flaw in mysql-connector-odbc allows an unauthenticated attacker with local logon access to the system to cause a complete denial of service and gain unauthorized read access to a subset of data. The local attack vector limits the immediate remote exploitability, but successful exploitation can significantly impact system availability and data confidentiality.

Mitigation

Since this vulnerability requires local logon access, ensure that only trusted users have interactive access to systems running `mysql-connector-odbc`. If the `mysql-connector-odbc` package is not actively used, consider removing it to eliminate the attack surface.

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 Score6.8N/A6.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/ALow
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.