Skip to main content
Menu
CVEs

MapServer SQL injection in PostgreSQL JOIN support

CVE-2026-77328Published , updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 8.6.5
Who is exposed
Not reported

Summary

In MapServer, when PostgreSQL JOIN support is enabled, an attacker who can control a source feature attribute can inject SQL that alters the intended query, returning unintended rows and JOIN attributes and potentially exposing data from unrelated PostgreSQL records. The flaw can be reached remotely over the network without logging in and without any user action.

Written by a model

Original description

MapServer is a system for developing web-based GIS applications. Prior to 8.6.5, MapServer's PostgreSQL JOIN implementation in src/mappostgresql.c copies the source layer attribute selected by JOIN FROM into joininfo->from_value and embeds it without parameterization or escaping into a dynamically generated PostgreSQL query executed by PQexec(). When PostgreSQL JOIN support is enabled, an attacker who can control that source feature attribute can inject quote characters and SQL operators that alter the intended WHERE predicate. This second-order injection can cause unintended rows and JOIN attributes to be returned, potentially exposing information from unrelated PostgreSQL records. This issue is fixed in version 8.6.5.

What to do

Upgrade to a fixed version: 8.6.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77328 (MapServer: PostgreSQL JOIN second-order SQL injection in src/mappostgresql.c), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77328 (entry last updated 2026-11-20):
Affected:
- MapServer MapServer: fixed in 8.6.5
Fixed versions: 8.6.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77328 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77328 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/MapServer/MapServer/security/advisories/GHSA-m3xh-ccmh-x8rw
- https://github.com/MapServer/MapServer/pull/7546
- https://github.com/MapServer/MapServer/pull/7566
- https://github.com/MapServer/MapServer/commit/05babb88314b8f022eb47a3ab1a00eb37f92085f
- https://github.com/MapServer/MapServer/commit/a39a299a03a767dd966bb40caf044539e7813bce
- https://github.com/MapServer/MapServer/releases/tag/rel-8-6-5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77328
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77328"}.

Affected versions

cve.now Index

24Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 8

Questions about CVE-2026-77328

Is CVE-2026-77328 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77328?

MapServer: before 8.6.5.

Source: cve.now feed data

How do I fix CVE-2026-77328?

Upgrade to a fixed version: 8.6.5.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.