MEDIUM CVSS 5.0
Published: 2026-06-12

CVE-2026-44173

mariadb mariadb Security Advisory (CVE-2026-44173)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-44173?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-44173 impacting mariadb mariadb. Evaluated with CVSS Base Score of 5.0 (MEDIUM).

Original NVD Description

Source: NIST NVD
MariaDB server is a community developed fork of MySQL server. From versions 10.6.1 to before 10.6.26, 10.11.1 to before 10.11.17, 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, MariaDB allowed SELECT ... INTO OUTFILE and SELECT ... INTO DUMPFILE without verifying the FILE privilege if the FROM clause contained only subqueries. This issue has been patched in versions 10.6.26, 10.11.17, 11.4.11, 11.8.7, and 12.3.2.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
None (C:N)
No data confidentiality impact
Integrity
None (I:N)
No system modification impact
Availability
Low (A:L)
Partial service performance degradation

🎯 Affected Versions Matrix

Affected Product mariadb / mariadb
Affected Versions *
Weakness Enumeration CWE-863

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-44173 impacting mariadb mariadb.

⚡ Nuclei Detection Template (YAML) cve-2026-44173.yaml
id: cve-2026-44173

info:
  name: mariadb mariadb - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: medium
  description: |
    Automated signature & scanner for CVE-2026-44173 affecting mariadb mariadb.
    Evaluation: MariaDB server is a community developed fork of MySQL server. From versions 10.6.1 to before 10.6.26, 10.11.1 to before 10.11.17, 11.4.1 to before 11....
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-44173
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L
    cvss-score: 5.0
    cve-id: CVE-2026-44173
    cwe-id: CWE-863
  tags: cve,cve-2026-44173,mariadb,mariadb,medium

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "mariadb"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-44173.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-44173
# Target: mariadb mariadb | CVSS: 5.0 (MEDIUM)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-44173 (mariadb mariadb)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against mariadb mariadb scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-44173.sh
# Recommended Remediation & Patching Commands for CVE-2026-44173
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install mariadb 2>/dev/null || \
sudo dnf upgrade mariadb 2>/dev/null || \
sudo yum update mariadb

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i mariadb 2>/dev/null || rpm -qa | grep -i mariadb

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-44173 in mariadb mariadb?

Review vendor-specific security notices and update mariadb mariadb packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-44173?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-44173?

CVE-2026-44173 is classified with a CVSS 3.1 Base Score of 5.0 (MEDIUM). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
5.0
MEDIUM SEVERITY
CVE ID CVE-2026-44173
Weakness CWE-863
Vendor mariadb
Product mariadb
Published 2026-06-12
Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L