Skip to main content

MySQL Connector/J EUVDEUVD-2026-106169

| CVE-2026-101768 HIGH
Improper Access Control (CWE-284)
2026-10-20 secalert_us@oracle.com GHSA-5rjv-7cpf-g6jj
8.1
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure/redirect client to malicious MySQL endpoint
  2. Exploit
    Return crafted server protocol response
  3. Execution
    Trigger flaw in Connector/J driver
  4. Impact
    Compromise Java client application

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets MySQL Connector/J 26.7.0 specifically and, consistent with AC:H, is not a straightforward remote hit against a default listener: the realistic prerequisite is that the attacker controls, compromises, or can man-in-the-middle the MySQL server endpoint that a Java application using the driver connects to, so that a malicious/crafted server response is processed by the vulnerable driver. Limiting factors: only version 26.7.0 is listed as affected (upgrade/downgrade removes exposure), the 'Difficult to exploit' (AC:H) rating implies additional attacker-uncontrolled conditions must be met, and the application must actually initiate a connection to an attacker-influenced endpoint - pure internet-facing unauthenticated mass exploitation is unlikely despite PR:N/UI:N. Oracle does not disclose the exact feature or configuration flag involved.

Impact

This is a serious-on-paper but exploitation-constrained issue. The CVSS 3.1 base score is 8.1 (HIGH) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning network-reachable, unauthenticated (PR:N), no user interaction, and full confidentiality/integrity/availability loss ('takeover'). The single most important mitigating signal is AC:H - Oracle's own wording 'Difficult to exploit' - which indicates the attacker does not control all preconditions and must win a non-trivial, situation-dependent condition. No EPSS score was supplied, no CISA KEV listing is present, and no public exploit is indicated, so there is no public exploit identified at time of analysis; this is not evidence of active exploitation. No SSVC decision data was provided. Signals are therefore consistent rather than conflicting: a high technical impact tempered by genuine exploitation difficulty and no observed in-the-wild activity. Note a metadata discrepancy to verify: the input Tag labels this 'Information Disclosure', yet the description and CVSS (C:H/I:H/A:H, 'takeover') describe full compromise, not mere disclosure - treat the impact as full takeover per Oracle's own CVSS.

Exploit ScenarioDerived

Connector/J is MySQL's JDBC client driver, so the realistic path is server-to-client: an attacker who controls or can MITM the MySQL endpoint a Java application connects to returns a crafted protocol response that the driver mishandles, leading to compromise of the client application. The AC:H rating reflects that the attacker must first be positioned as (or intercept) the database server and satisfy additional conditions, which is why it is rated difficult. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

MySQL Connector/J 26.7.0 can be fully compromised - confidentiality, integrity and availability - when a Java application using the driver processes a crafted or attacker-controlled response from the MySQL server endpoint it connects to, giving the attacker a path to take over the connector. Oracle scores this 8.1 but rates attack complexity High despite PR:N/UI:N, reflecting that the realistic precondition is attacker control of, or man-in-the-middle position on, the database endpoint rather than a direct hit on an internet-facing listener. No public exploit code and no CISA KEV entry were identified at time of analysis, and only version 26.7.0 is listed as affected, so upgrading removes exposure.

RemediationAI

Apply the fix from Oracle's October 2026 Critical Patch Update (https://www.oracle.com/security-alerts/cpuoct2026.html) and move Connector/J off 26.7.0 to the corrected driver release Oracle designates in that advisory; the exact patched version number is not published in the supplied data, so confirm it against the CPU before rollout, then rebuild and redeploy every application, container image, and shaded/fat JAR that embeds the driver and refresh dependency manifests to block re-introduction. Because exploitation hinges on a hostile or intercepted database endpoint, enforce TLS with server certificate validation from the client (for example MySQL Connector/J sslMode=VERIFY_IDENTITY or VERIFY_CA with a trusted CA bundle) to defeat man-in-the-middle responses; the trade-off is that self-signed or misconfigured development servers will fail to connect until their certificates are fixed. Additionally, restrict outbound JDBC connectivity so applications can only reach approved database hosts, which contains the impact if credentials or connection strings are abused, at the cost of added firewall/egress policy maintenance. Where the driver cannot be upgraded immediately, pinning and verifying server certificates combined with strict egress allow-listing are the most effective compensating controls, but they reduce rather than eliminate exposure and should be treated as temporary.

Affected VersionsENISA

MySQL Connectors 26.7.0

Affected Packages

euvd mysql_connectors no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw lives in Oracle's Connector/J, the Type 4 JDBC driver Java applications use to speak the MySQL client/server protocol over TCP (and HTTP-tunneled transports in some deployments). Because the driver parses and acts on data supplied by the server during connection setup and normal query processing, an adversary who controls, compromises, or intercepts the MySQL endpoint can feed malicious responses into the vulnerable 26.7.0 driver code and trigger the impact. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms the attack is network-reachable and requires no credentials or user interaction, but AC:H signals attacker-uncontrolled conditions must also line up - consistent with the assessment that a hostile or spoofed server endpoint must first be reached by the application. Oracle has not disclosed the specific component feature, code path, or configuration flag involved, and no CWE was assigned in the supplied data; the third-party 'Information Disclosure' tag is narrower than the full C/I/A impact in the vendor vector and should not be read as limiting the blast radius. Only MySQL Connectors 26.7.0 is enumerated as affected (EUVD), so the vulnerable surface is the driver version rather than a server-side listener.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Concur with Oracle: network driver reachable over HTTP/protocol (AV:N), no auth or interaction (PR:N/UI:N), but attacker must control the responding server and meet extra conditions (AC:H); full client takeover gives C:H/I:H/A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). The supported version that is affected is 26.7.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Executive ViewAI

Why It Matters

MySQL Connector/J 26.7.0, the Java driver used by applications to connect to MySQL, can be fully compromised across confidentiality, integrity, and availability when it processes attacker-controlled responses from the database endpoint. Applications using this exact driver version are exposed, especially where database endpoints are not strictly trusted or where man-in-the-middle risk exists; leadership should prioritize inventory and endpoint-trust controls because exploitation could undermine application data and service availability.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim controls: enforce TLS with strict certificate validation, restrict Connector/J 26.7.0 to trusted MySQL endpoints, segment database network paths, monitor for man-in-the-middle activity, and upgrade off 26.7.0 to a vendor-validated release.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
High
MySQL Connector/J is a ubiquitous JDBC driver, but only v26.7.0 is affected
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy