LiveActive security incident?Get immediate response
CVE Record

CVE-2026-33721: MapServer has heap buffer overflow in SLD `Categorize` Threshold parsing

MapServer is a system for developing web-based GIS applications. Starting in version 4.2 and prior to version 8.6.1, a heap-buffer-overflow write in MapServer’s SLD (Styled Layer Descriptor) parser lets a remote, unauthenticated attacker crash the MapServer process by sending a crafted SLD with more than 100 Threshold elements inside a ColorMap/Categorize structure (commonly reachable via WMS GetMap with SLD_BODY). Version 8.6.1 patches the issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-33721 is a denial-of-service flaw in MapServer’s SLD parsing. A remote unauthenticated user can crash the MapServer process if the service accepts crafted SLD input, commonly through WMS GetMap with SLD_BODY. It affects MapServer versions 4.2 through before 8.6.1. The documented fix is upgrading to 8.6.1.

Executive priority

Treat as a timely availability risk for public GIS services. Prioritize internet-facing or business-critical MapServer deployments, especially those accepting user-supplied styling. This is not currently evidenced as actively exploited, but the attack requires no authentication and low complexity.

Technical view

MapServer has a heap-buffer-overflow write in SLD ColorMap/Categorize Threshold parsing when more than 100 Threshold elements are processed. The issue is CWE-787 with CVSS 5.3, AV:N/AC:L/PR:N/UI:N, impacting availability only per the provided vector. The advisory states version 8.6.1 patches the vulnerability.

Likely exposure

Exposure is likely where MapServer versions older than 8.6.1 are internet-facing or reachable by untrusted users and support SLD input, especially WMS GetMap requests using SLD_BODY. Systems not using MapServer, already on 8.6.1, or not accepting untrusted SLD content are less exposed based on available sources.

Exploitation context

The sources describe remote unauthenticated crash potential, but do not indicate confirmed active exploitation. The CVE is not listed as KEV in the provided data. The known impact is availability loss from process crash, not confidentiality or integrity compromise.

Researcher notes

The key exposure condition is SLD ColorMap/Categorize Threshold parsing in MapServer before 8.6.1. Keep validation non-invasive in production; confirm version and configuration rather than attempting crash reproduction. Debian LTS communication suggests downstream packaging may have separate update paths.

Mitigation direction

  • Upgrade MapServer to version 8.6.1 or later.
  • Review MapServer and distribution vendor advisories for packaged fixes.
  • Limit untrusted SLD input where operationally feasible.
  • Restrict public access to affected WMS endpoints if not required.

Validation and detection

  • Inventory MapServer deployments and confirm running versions.
  • Identify services exposing WMS GetMap or SLD_BODY handling.
  • Check whether MapServer packages include the 8.6.1 fix.
  • Review logs and monitoring for unexplained MapServer crashes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-33721 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-33721Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MapServerMapServer>= 4.2, < 8.6.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.