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.
CVE-2026-77326
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0% (62nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-131826 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.6
- EG Score
- 8.6HIGHlow confidence
- EG Risk
- 70EG Risk 70/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity86% × 45%Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.0%
- EPSS %ILE
- 62nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 1.0% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 20, 2026
Last Modified
November 20, 2026
Advisory Details (6)
Auto-updated Nov 20, 2026MapServer 8.6.5
Patch available: MapServer/MapServer rel-8-6-5
https://github.com/MapServer/MapServer/releases/tag/rel-8-6-5commit ea1d87a6d45b (MapServer/MapServer)
Fix landed in MapServer/MapServer commit ea1d87a6d45b — awaiting tagged release
https://github.com/MapServer/MapServer/commit/ea1d87a6d45bbe5814a545a8b4d6a5e6b6842ea8commit a7d5eb844a59 (MapServer/MapServer)
Patch available: MapServer/MapServer rel-8-6-5 (contains commit a7d5eb844a59)
https://github.com/MapServer/MapServer/commit/a7d5eb844a59ea076b7972a018753242f18e6f7b[Backport branch-8-6] WMS: GetLegendGraphic: avoid potential write heap buffer overflow via repeated LAYER parameters
Patch available: MapServer/MapServer rel-8-6-5 (PR #7569 merged 2026-07-09)
https://github.com/MapServer/MapServer/pull/7569WMS: GetLegendGraphic: avoid potential write heap buffer overflow via repeated LAYER parameters
Fix merged in MapServer/MapServer PR #7555 on 2026-07-08 — awaiting tagged release
https://github.com/MapServer/MapServer/pull/7555MapServer 8.6.4: Heap buffer overflow in WMS GetLegendGraphic via repeated LAYER parameters · Advisory · MapServer/MapServer · GitHub
https://github.com/MapServer/MapServer/security/advisories/GHSA-4mwc-qc95-5959Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-22 07:56 UTCOSV refresh
- 2026-11-21 16:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-11-20 21:04 UTCENISA EUVD ID recordedEUVD-2026-131826 · Source: ENISA EUVD
- 2026-11-20 20:28 UTCEchelonGraph re-scored
- 2026-11-20 19:42 UTCEchelonGraph re-scored
- 2026-11-20 19:27 UTCEchelonGraph re-scored
- 2026-11-20 19:18 UTCEchelonGraph re-scoredFirst assessed: 8.6 HIGH
- 2026-11-20 19:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-77326?
When was the CVE record for CVE-2026-77326 published?
Is CVE-2026-77326 actively exploited?
What is the CVSS score of CVE-2026-77326?
How do I remediate CVE-2026-77326?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77326
Is Your Infrastructure Affected by CVE-2026-77326?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.