MapServer is a system for developing web-based GIS applications. Prior to 8.6.5, MapServer's MySQL JOIN implementation in src/mapjoin.c copies the source layer attribute selected by JOIN ... FROM into joininfo->target and inserts it into the query built by msMySQLJoinNext() without parameterization or SQL escaping. When MySQL JOIN support is enabled, an attacker who can control that source feature attribute, including through imported shapefile or DBF data or another untrusted spatial source, can inject SQL operators or expressions that change the intended JOIN predicate. This can bypass the intended key comparison and expose unrelated records from the MySQL or MariaDB JOIN table through output templates, query responses, or downstream application logic. This issue is fixed in version 8.6.5.
1.2% estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-89Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
Show the promptExplain CVE-2026-77327 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77327?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77327?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77327 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.
Attack patterns (CAPEC)
CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
CAPEC-66 SQL Injection Likelihood: High · Severity: High
CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.