dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-22314

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

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
Improper Control of Generation of Code ('Code Injection') vulnerability in Mesalvo Meona Client Launcher Component, Mesalvo Meona Server Component enables code execution on other users' systems. This issue affects Meona Client Launcher Component: through 19.06.2020 15:11:49; Meona Server Component: through 2025.04 5+323020.

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 code injection vulnerability in Mesalvo Meona allows attackers to inject and execute arbitrary code on affected systems. The vulnerability exists in both the Client Launcher Component and Server Component, potentially allowing an attacker to execute malicious code on other users' systems. This is a critical flaw in input validation that permits untrusted data to be interpreted as executable code.

MitigationApply vendor-supplied patches for both Meona Client Launcher and Server Components. Until patches are available, restrict network access to server components and implement application-layer filtering. Given this is a healthcare application, immediate prioritization is critical due to the CVSS 9 severity and potential for lateral movement.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 Meona Client Launcher installation
    Locate the Meona Client Launcher installation directory and look for version information in launcher configuration files, about dialogs, or installed program metadata (Windows: Check Programs and Features, Linux: check /opt/meona or similar installation paths)
    Affected if Installed version is June 2020 or earlier (no patch version beyond June 2020 releases)
  2. Identify Meona Server Component installation
    Locate the Meona Server installation and retrieve version information from server configuration files, administration console, or service information
    Affected if Installed version is April 2025 or earlier (no patch version beyond April 2025 releases)
  3. Verify Client Launcher network accessibility
    Check if the Client Launcher component is exposed to network access by reviewing firewall rules, listening ports (common Meona launcher ports), or network configuration settings
    Affected if Client Launcher component is network-accessible from untrusted zones
  4. Verify Server Component network accessibility
    Review network configuration, listening services, and firewall rules to determine if the Meona Server Component accepts connections from network endpoints
    Affected if Server Component is network-accessible without proper authentication or input validation controls
  5. Inspect code injection points
    Examine Meona configuration files, particularly those controlling client-server communication, message handling, or plugin/extension loading mechanisms for lack of input validation settings
    Affected if Configuration allows arbitrary code execution or lacks input validation on data received from clients or sent between components

Your environment is affected if you are running Meona Client Launcher versions through June 2020 or Meona Server Component versions through April 2025, and these components are network-accessible without compensating controls.

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

Apply vendor-supplied patches for both Meona Client Launcher and Server Components. Until patches are available, restrict network access to server components and implement application-layer filtering. Given this is a healthcare application, immediate prioritization is critical due to the CVSS 9 severity and potential for lateral movement.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22314 — 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-22314 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