HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 61700 mariadb connectorj does not enforce
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Low · CVSS 3.7CVE-2026-61700GHSA-WXMM-Q36W-R9XJ

MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requestsCVE-2026-61700

Answer in brief

CVE-2026-61700 records a Low severity (CVSS 3.7) vulnerability in MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests. The current sources do not mark it as known exploited. The current feed maps mariadb-corporation/mariadb-connector-j (generic), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 23, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 2026Material review Sep 23, 2026
Upstream Advisory

Key facts

Risk
Low · CVSS 3.7
Exploitation
Not marked as known exploited
Affected software
9 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps mariadb-corporation/mariadb-connector-j (generic), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
mariadb-corporation/mariadb-connector-jgeneric<2.7.14 || >=3.0.0 <3.3.5 || >=3.4.0 <3.4.3 || >=3.5.0 <3.5.92.7.14, 3.3.5, 3.4.3, 3.5.9
org.mariadb.jdbc:mariadb-java-clientmaven<2.7.142.7.14
org.mariadb.jdbc:mariadb-java-clientmaven>=3.0.0,<3.3.53.3.5
org.mariadb.jdbc:mariadb-java-clientmaven>=3.4.0,<3.4.33.4.3
org.mariadb.jdbc:mariadb-java-clientmaven>=3.5.0,<3.5.93.5.9
org.mariadb.jdbc:mariadb-java-clientmaven>=0 <2.7.142.7.14
org.mariadb.jdbc:mariadb-java-clientmaven>=3.0.0 <3.3.53.3.5
org.mariadb.jdbc:mariadb-java-clientmaven>=3.4.0 <3.4.33.4.3
org.mariadb.jdbc:mariadb-java-clientmaven>=3.5.0 <3.5.93.5.9

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for mariadb-corporation/mariadb-connector-j, org.mariadb.jdbc:mariadb-java-client, org.mariadb.jdbc:mariadb-java-client.
  2. 2Review the reported fix. Update mariadb-corporation/mariadb-connector-j to 2.7.14; org.mariadb.jdbc:mariadb-java-client to 2.7.14; org.mariadb.jdbc:mariadb-java-client to 3.3.5; org.mariadb.jdbc:mariadb-java-client to 3.4.3; org.mariadb.jdbc:mariadb-java-client to 3.5.9; org.mariadb.jdbc:mariadb-java-client to 2.7.14; org.mariadb.jdbc:mariadb-java-client to 3.3.5; org.mariadb.jdbc:mariadb-java-client to 3.4.3; org.mariadb.jdbc:mariadb-java-client to 3.5.9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Sep 23, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Sep 17, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, ClientMessage.readPacket processes a server-initiated LOCAL INFILE protocol packet 0xfb without enforcing allowLocalInfile=false. When an application sends a LOAD DATA LOCAL INFILE COM_QUERY, a rogue or man-in-the-middle server can echo the same filename and cause the connector to transmit that file despite the disabled option. The server cannot redirect the request to an arbitrary path and can receive only the exact file already selected by the application, so exploitation requires an application that actively loads sensitive data over an untrusted connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Gitea admin API public-only token scope bypassAlso CWE-284
  • ag-ui-protocol ag-ui HttpAgent http.ts information disclosureAlso CWE-284

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-284
Source
CVE List V5
Source checked
Nov 1, 2026
References
5 linked sources
Open source record