CVE-2026-77327

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2% (68th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
Elevated

Also known asEUVD-2026-131823 (ENISA EUVD)Source: ENISA EUVD

6.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 6.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

MapServer is a system for developing web-based GIS applications. Prior to 8.6.5, MapServer's MySQL JOIN implementation in src/mapjoin.c copies the source layer attribute selected by JOIN ... FROM into joininfo->target and inserts it into the query built by msMySQLJoinNext() without parameterization or SQL escaping. When MySQL JOIN support is enabled, an attacker who can control that source feature attribute, including through imported shapefile or DBF data or another untrusted spatial source, can inject SQL operators or expressions that change the intended JOIN predicate. This can bypass the intended key comparison and expose unrelated records from the MySQL or MariaDB JOIN table through output templates, query responses, or downstream application logic. This issue is fixed in version 8.6.5.

CVSS
6.9
EG Score
6.9MEDIUMlow confidence
EG Risk
62
EG Risk 62/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 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.2%
EPSS %ILE
68th
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
1.2% 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, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

MapServer 8.6.5

Patch available: MapServer/MapServer rel-8-6-5

https://github.com/MapServer/MapServer/releases/tag/rel-8-6-5
GitHub commit Patch Available

commit f4f95059e261 (MapServer/MapServer)

Patch available: MapServer/MapServer rel-8-6-5 (contains commit f4f95059e261)

https://github.com/MapServer/MapServer/commit/f4f95059e2610d431e0b46d75d713cd52b84f64c
GitHub commit

commit b1aa22b1ea4b (MapServer/MapServer)

Fix landed in MapServer/MapServer commit b1aa22b1ea4b — awaiting tagged release

https://github.com/MapServer/MapServer/commit/b1aa22b1ea4ba4293c0fddea92e01ce0dc18a300
GitHub pull request Patch Available

[Backport branch-8-6] msMySQLJoinNext(): prevent SQL injection

Patch available: MapServer/MapServer rel-8-6-5 (PR #7567 merged 2026-07-09)

https://github.com/MapServer/MapServer/pull/7567
GitHub pull request

msMySQLJoinNext(): prevent SQL injection

Fix merged in MapServer/MapServer PR #7547 on 2026-07-08 — awaiting tagged release

https://github.com/MapServer/MapServer/pull/7547
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

MapServer 8.6.4: MySQL JOIN second-order SQL injection in src/mapjoin.c · Advisory · MapServer/MapServer · GitHub

https://github.com/MapServer/MapServer/security/advisories/GHSA-7624-4mwh-9cxr

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× 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 → 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.

  1. 2026-11-21 16:41 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  2. 2026-11-20 21:04 UTCENISA EUVD ID recordedEUVD-2026-131823 · Source: ENISA EUVD
  3. 2026-11-20 20:30 UTCEchelonGraph re-scored
  4. 2026-11-20 19:42 UTCEchelonGraph re-scored
  5. 2026-11-20 19:27 UTCEchelonGraph re-scored
  6. 2026-11-20 19:18 UTCEchelonGraph re-scoredFirst assessed: 6.9 MEDIUM
  7. 2026-11-20 19:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77327?
CVE-2026-77327 is a medium-severity vulnerability; its CVE record was published on November 20, 2026. MapServer is a system for developing web-based GIS applications. Prior to 8.6.5, MapServer's MySQL JOIN implementation in src/mapjoin.c copies the source layer attribute selected by JOIN ... FROM into joininfo->target and inserts it into the query built by msMySQLJoinNext() without parameterization…
When was the CVE record for CVE-2026-77327 published?
The CVE record for CVE-2026-77327 was published on November 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-77327 actively exploited?
CVE-2026-77327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (68th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77327?
CVE-2026-77327 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-77327?
A fix for CVE-2026-77327 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77327

Explore →

Is Your Infrastructure Affected by CVE-2026-77327?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.