MapServer denial of service in WCS POST via BoundingBox
Affects MapServer from 4.4.0 onward when WCS support is in use and a GetCoverage XML POST has a BoundingBox without the crs attribute. Fixed in 8.6.5.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.6.5
- Who is exposed
- Default setups
Summary
MapServer is affected: an unauthenticated remote attacker can send a crafted WCS GetCoverage XML POST request whose BoundingBox element lacks the crs attribute, crashing the CGI or FastCGI worker and denying service, and repeated requests can exhaust the worker pool.
Written by a model
Original description
MapServer is a system for developing web-based GIS applications. From 4.4.0 until 8.6.5, an unauthenticated remote attacker can send a WCS GetCoverage XML POST request whose BoundingBox element omits the crs attribute, causing xmlGetProp() in src/mapwcs.cpp to return null. msWCSParseRequest() then calls string functions on the null value before normal WCS exception handling, crashing the CGI or FastCGI worker. The analogous KVP or GET path is not affected because it obtains a count-validated, non-null token. A single request can terminate one worker, and repeated requests can exhaust a fixed worker pool and deny service. This issue is fixed in version 8.6.5.
Who should check
Anyone running MapServer 4.4.0 or later with WCS enabled and exposed through mapserv CGI or FastCGI.
“WCS support in MapServer”
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-77324 (MapServer: WCS POST: NULL-Dereference Denial of Service When `BoundingBox` Omits `crs`), 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-77324 (entry last updated 2026-11-20):
Affected:
- MapServer MapServer: from 4.4.0, fixed in 8.6.5
Fixed versions: 8.6.5.
Conditions (all must be true for the bug to be hit):
- MapServer WCS support is in use, from version 4.4.0 onward (source: https://github.com/MapServer/MapServer/security/advisories/GHSA-35qh-49hm-5rcx)
- A WCS GetCoverage request is sent as an XML POST whose BoundingBox element lacks the crs attribute (source: https://github.com/MapServer/MapServer/security/advisories/GHSA-35qh-49hm-5rcx)
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-77324 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77324 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-35qh-49hm-5rcx
- https://github.com/MapServer/MapServer/pull/7556
- https://github.com/MapServer/MapServer/pull/7568
- https://github.com/MapServer/MapServer/commit/3d2bed5de60b2947e39c608cfad4b31d56aeae0e
- https://github.com/MapServer/MapServer/commit/debd347ae53caa4969f87fd9dae5ff73a42d48a0
- 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-77324
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-77324"}.Affected versions
- MapServer MapServerFrom 4.4.0 · fixed in 8.6.5
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · MapServer/MapServer · Advisory GHSA-35qh-49hm-5rcx |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77324 |
| Record | NVD · CVE-2026-77324 |
| Other links 5 | |
| Repository | GitHub · MapServer/MapServer · Pull request #7556 |
| Repository | GitHub · MapServer/MapServer · Pull request #7568 |
| Repository | GitHub · MapServer/MapServer · Commit 3d2bed5d |
| Repository | GitHub · MapServer/MapServer · Commit debd347a |
| Repository | GitHub · MapServer/MapServer · Release rel-8-6-5 |
Questions about CVE-2026-77324
Is CVE-2026-77324 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
What does this mean?
A single crafted WCS GetCoverage POST request whose BoundingBox element omits the crs attribute crashes the CGI or FastCGI worker. Repeated requests can exhaust the worker pool, so this is a denial-of-service flaw.
Source: github.com
Which versions are affected by CVE-2026-77324?
MapServer: from 4.4.0 before 8.6.5.
Source: cve.now feed data
Am I affected, and how do I check?
The flaw affects MapServer from 4.4.0 up to, but not including, 8.6.5, and only where WCS support is in use. To check, look at the installed MapServer version and whether the WCS service is enabled in the mapfile.
Source: github.com
How do I fix CVE-2026-77324?
Upgrade MapServer to 8.6.5 or later, which is the listed fixed version.
Source: github.com
Related
- CVE-2025-59431MapServer - WFS XML Filter Query SQL injection
- CVE-2026-77326MapServer: Heap buffer overflow in WMS GetLegendGraphic via repeated LAYER parameters
- CVE-2026-54354MapServer: PostGIS Numeric Filter Value SQL Injection in MapServer Runtime Query Translation
- 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.