MapServer remote code execution risk in WMS GetLegendGraphic
Affects MapServer 8.2.0 through 8.6.4 and main when built with WMS server support and a mapfile layer enables GetLegendGraphic. Fixed in 8.6.5.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 8.6.5
- Who is exposed
- Default setups
Summary
MapServer has a heap buffer overflow in its WMS GetLegendGraphic handling, triggered by a request with a nonempty BBOX and repeated LAYER parameters. An unauthenticated attacker can send that request over the network to corrupt heap memory and crash the process, and code execution may be possible but has not been demonstrated.
Written by a model
Original description
MapServer is a system for developing web-based GIS applications. From 8.2.0 until 8.6.5, an unauthenticated attacker can send a WMS GetLegendGraphic request with a nonempty BBOX and repeated LAYER parameters to trigger a heap buffer overflow in msWMSDispatch() in src/mapwms.cpp. The handler appends synthesized entries to cgiRequestObj.ParamNames and cgiRequestObj.ParamValues at NumParams without retaining the arrays' capacity or reallocating them, while incrementing NumParams inside the loop. Once the parser's hidden capacity is exhausted, the writes pass the heap allocation boundary. A single request can corrupt heap memory and crash the process; code execution may be possible but was not demonstrated. This issue is fixed in version 8.6.5.
Who should check
Teams running MapServer 8.2.0 through 8.6.4 (or main) with WMS server enabled and GetLegendGraphic exposed to the internet
“Versions 8.2.0–8.6.4 and main”
What to do
Check every install: default setups are affected.
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-77326 (MapServer: Heap buffer overflow in WMS GetLegendGraphic via repeated LAYER parameters), 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-77326 (entry last updated 2026-11-20):
Affected:
- MapServer MapServer: fixed in 8.6.5
Fixed versions: 8.6.5.
Conditions (all must be true for the bug to be hit):
- MapServer versions 8.2.0 through 8.6.4, and main (source: https://github.com/MapServer/MapServer/security/advisories/GHSA-4mwc-qc95-5959)
- Request is a WMS GetLegendGraphic with a non-empty BBOX and repeated LAYER parameters (source: https://github.com/MapServer/MapServer/security/advisories/GHSA-4mwc-qc95-5959)
- MapServer is built with WMS server support, which is on by default (source: https://github.com/MapServer/MapServer/security/advisories/GHSA-4mwc-qc95-5959)
- A mapfile layer has wms_enable_request including GetLegendGraphic (source: https://github.com/MapServer/MapServer/security/advisories/GHSA-4mwc-qc95-5959)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77326 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77326 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-4mwc-qc95-5959
- https://github.com/MapServer/MapServer/pull/7555
- https://github.com/MapServer/MapServer/pull/7569
- https://github.com/MapServer/MapServer/commit/a7d5eb844a59ea076b7972a018753242f18e6f7b
- https://github.com/MapServer/MapServer/commit/ea1d87a6d45bbe5814a545a8b4d6a5e6b6842ea8
- 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-77326
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-77326"}.Affected versions
- MapServer MapServerfixed in 8.6.5
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure25/25Default setups, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · MapServer/MapServer · Advisory GHSA-4mwc-qc95-5959 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77326 |
| Record | NVD · CVE-2026-77326 |
| Other links 5 | |
| Repository | GitHub · MapServer/MapServer · Pull request #7555 |
| Repository | GitHub · MapServer/MapServer · Pull request #7569 |
| Repository | GitHub · MapServer/MapServer · Commit a7d5eb84 |
| Repository | GitHub · MapServer/MapServer · Commit ea1d87a6 |
| Repository | GitHub · MapServer/MapServer · Release rel-8-6-5 |
Questions about CVE-2026-77326
Is CVE-2026-77326 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A heap buffer overflow in the WMS GetLegendGraphic request crashes the MapServer process when the request has a non-empty BBOX and repeated LAYER parameters. A single HTTP request is enough to crash it, which is a denial of service. Remote code execution was not demonstrated.
Source: github.com
Which versions are affected by CVE-2026-77326?
MapServer: before 8.6.5.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 8.2.0 through 8.6.4, and main, are affected. The setup also needs WMS server support, which is on by default, and at least one mapfile layer with wms_enable_request including GetLegendGraphic. To check a version, run mapserv -v on the installed binary.
Source: github.com
How do I fix CVE-2026-77326?
Upgrade to MapServer 8.6.5 or later.
Source: github.com
Related
- CVE-2025-59431MapServer - WFS XML Filter Query SQL injection
- CVE-2026-54354MapServer: PostGIS Numeric Filter Value SQL Injection in MapServer Runtime Query Translation
- CVE-2026-77324MapServer: WCS POST: NULL-Dereference Denial of Service When `BoundingBox` Omits `crs`
- CVE-2026-45104MapServer: NULL pointer dereference in SLD `<ElseFilter>` rule parsing reachable via WMS `SLD_BODY`
- CVE-2026-77328MapServer: PostgreSQL JOIN second-order SQL injection in src/mappostgresql.c
- CVE-2026-77327MapServer: MySQL JOIN second-order SQL injection in src/mapjoin.c
No corrections so far. Something wrong on this page? Report an error.