CRITICAL CVSS 10.0
Published: 2026-06-19

CVE-2026-48772

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

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-48772 impacting Software Component. Evaluated with CVSS Base Score of 10.0 (CRITICAL).

Original NVD Description

Source: NIST NVD
ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the `PROXY UNKNOWN <addr> <addr> <port> <port>\r\n` PP1 frame as a well-formed PROXY protocol header. The HAProxy PROXY protocol v1 specification says that when the protocol token is `UNKNOWN`, the receiver MUST ignore any address fields that follow it, because the proxy has declared it cannot determine the client identity. ProxySQL parses those address fields anyway via `sscanf` and writes the spoofed source address into the session's `addr.addr` field. From there it flows directly into the query-rule matcher, where the `client_addr` predicate decides routing and ACL. When `mysql-proxy_protocol_networks = '*'` (the default), any TCP peer can send a PP1 frame and choose any source IP claim. With that, any `mysql_query_rules` row pinned to a `client_addr` value is forgeable: the attacker writes the address they want to match into the PP1 line, and ProxySQL routes their query as if it came from that address. In practice this is a routing and ACL bypass. Real deployments use `client_addr` for read-write splitting (internal apps go to the primary, public traffic to read replicas), per-app schema pinning, and query-filter rules (DDL allowed only from admin CIDR, public queries blocked from dangerous patterns). An attacker that can reach the frontend port can forge their way into any of those routes. Version 3.0.9 patches this issue.

📊 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
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product Generic/Unknown / Software Component
Affected Versions Unspecified
Weakness Enumeration CWE-348

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-48772 impacting Software Component.

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

info:
  name: Software Component - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: critical
  description: |
    Automated signature & scanner for CVE-2026-48772 affecting Software Component.
    Evaluation: ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the `PROXY UN...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-48772
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
    cvss-score: 10.0
    cve-id: CVE-2026-48772
    cwe-id: CWE-348
  tags: cve,cve-2026-48772,generic,software,critical

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

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-48772 (Software Component)...")
    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 Software Component scope (Unspecified).")
        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-48772.sh
# Recommended Remediation & Patching Commands for CVE-2026-48772
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install software 2>/dev/null || \
sudo dnf upgrade software 2>/dev/null || \
sudo yum update software

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

# 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.

🔗 Verified Technical References

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-48772 in Software Component?

Review vendor-specific security notices and update Software Component 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-48772?

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-48772?

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

Risk Snapshot
10.0
CRITICAL SEVERITY
CVE ID CVE-2026-48772
Weakness CWE-348
Vendor Generic/Unknown
Product Software Component
Published 2026-06-19
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N