dbcve.org
Panda3dApplication · Cmu

CVE-2026-22189

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to after 1.10.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
The egg-mkfont utility in Panda3D versions up to and including 1.10.16 contains a stack-based buffer overflow vulnerability due to use of an unbounded sprintf() call with attacker-controlled input. When constructing glyph filenames, egg-mkfont formats a user-supplied glyph pattern (-gp) into a fixed-size stack buffer without length validation. Supplying an excessively long glyph pattern string can overflow the stack buffer, resulting in memory corruption and a deterministic crash. Depending on build configuration and execution environment, the overflow may also be exploitable for arbitrary code execution.

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 · high confidence

Stack-based buffer overflow in egg-mkfont utility in Panda3D versions up to 1.10.16. The -gp (glyph pattern) parameter is copied via unbounded sprintf() into a fixed-size stack buffer without length validation, allowing overflow and potential arbitrary code execution.

MitigationReplace sprintf() with bounded string functions (snprintf) and add input length validation for the -gp parameter before use.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Panda3dApplication
Affected:<= 1.10.16

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Locate the egg-mkfont utility
    Search for egg-mkfont in common Panda3D installation paths (e.g., /usr/bin, /usr/local/bin, or the Panda3D lib directory). Use 'which egg-mkfont' or 'find / -name egg-mkfont 2>/dev/null' to locate it.
    Affected if The egg-mkfont binary is present on the system.
  2. Determine the installed Panda3D version
    Run 'python3 -c "import panda3d; print(panda3d.__version__)"' or check the package manager for panda3d or panda3d-cmu version (e.g., 'pip show panda3d' or 'dpkg -l | grep panda3d').
    Affected if The version is 1.10.16 or any earlier version (1.10.x <= 1.10.16).
  3. Verify the -gp argument is in use
    Review any scripts, build processes, or automation that invoke egg-mkfont. Search for command lines containing 'egg-mkfont' and '-gp' or '--glyph-pattern'. Check shell history and configuration files for such invocations.
    Affected if The egg-mkfont utility is being called with the -gp (glyph pattern) argument.
  4. Confirm vulnerability trigger condition
    If egg-mkfont is present and -gp is used, note that the overflow occurs when a glyph pattern string of excessive length is passed to the -gp argument, overflowing a fixed-size stack buffer via sprintf().
    Affected if All three conditions are true: (1) egg-mkfont exists, (2) Panda3D version is <= 1.10.16, and (3) the -gp argument is being used with externally-supplied or untrusted input.

A user is affected if they have the egg-mkfont utility from Panda3D version 1.10.16 or earlier and are using it with the -gp (glyph pattern) command-line argument.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.10.16
Interim mitigation

Replace sprintf() with bounded string functions (snprintf) and add input length validation for the -gp parameter before use.

Recommended fix High confidence

Panda3D 1.10.17 or later

  1. Upgrade Panda3D to a version newer than 1.10.16 (such as 1.10.17 or latest stable release) to receive the fix for the unbounded sprintf() vulnerability in egg-mkfont
  2. If upgrade is not immediately possible, avoid using the egg-mkfont utility with user-supplied -gp (glyph pattern) parameters
  3. If egg-mkfont must be used, implement input validation to limit the -gp parameter to a safe length before passing to the utility
  4. Consider restricting access to systems where egg-mkfont is used to trusted users only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Panda3d Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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