dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-30479

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Dynamic-link Library Injection vulnerability in OSGeo Project MapServer before v8.0 allows attackers to execute arbitrary code via a crafted executable.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A Dynamic-link Library (DLL) Injection vulnerability in OSGeo Project MapServer versions before v8.0 allows attackers to execute arbitrary code by tricking the application into loading a malicious DLL or crafted executable into a running process.

MitigationUpgrade to MapServer v8.0 or later. Additionally, implement code signing for DLLs, restrict DLL search paths, and validate all executable inputs to prevent unauthorized code injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MapServer version
    Run 'mapserv -v' or 'mapserv --version' from the MapServer installation directory, or check the package manager if installed via apt/yum/dpkg/rpm
    Affected if The version displayed is lower than 8.0 (for example 7.x, 6.x, etc.)
  2. Verify CGI/MapServer executable location
    Locate the mapserv or mapserv.exe CGI executable (commonly in /usr/lib/cgi-bin/ on Linux or the CGI-BIN folder on Windows)
    Affected if The executable exists and is from a version before v8.0
  3. Check DLL search path configuration
    Review the MapServer configuration for any explicit DLL path settings, and verify if the server has insecure directories (current working directory, untrusted paths) in the system PATH
    Affected if DLL search paths are not restricted or the current working directory is in the DLL search order
  4. Inspect running MapServer processes
    Use process monitoring tools (Process Explorer on Windows, lsof/ps on Linux) to see which DLLs/executables the mapserv CGI process has loaded
    Affected if Any DLL loaded by the mapserv process originates from an untrusted or user-controlled location

You are affected if MapServer version is below v8.0 AND the application loads DLLs from configurable or untrusted paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to MapServer v8.0 or later. Additionally, implement code signing for DLLs, restrict DLL search paths, and validate all executable inputs to prevent unauthorized code injection.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30479 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data