dbcve.org
GhidraApplication · Nsa

CVE-2026-49498

HIGH · 8.8 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 12.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Ghidra 11.0 before 12.1 contains a SQL injection vulnerability in the changePassword() method of PostgresFunctionDatabase that fails to escape double quotes in usernames interpolated into ALTER ROLE statements. Authenticated attackers can inject SQL commands via crafted username parameters in PasswordChange network messages to escalate to PostgreSQL superuser privileges and gain full database control.

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

Ghidra 11.0 before 12.1 contains a SQL injection vulnerability in the changePassword() method of PostgresFunctionDatabase where double quotes in usernames are not properly escaped when interpolated into ALTER ROLE SQL statements. Authenticated attackers can send crafted PasswordChange network messages with specially crafted usernames to inject SQL commands, potentially escalating to PostgreSQL superuser privileges.

MitigationUpgrade to Ghidra 12.1 or later to obtain the patched version. As a defense-in-depth measure, implement proper input validation and use parameterized queries instead of string interpolation for all SQL statements.

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
GhidraApplication
Affected:>= 11.0, < 12.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check Ghidra installed version
    Launch Ghidra and navigate to Help > About Ghidra, or check the version field in the GhidraServer launch script (look for VERSION= or similar). On Linux, also check /opt/ghidra/ghidra_11.x/ or the installation directory for a version file.
    Affected if Version is 11.0 through 11.x (any version >= 11.0 and < 12.1)
  2. Identify database backend in use
    Examine the Ghidra server configuration file (usually ghidraServer.properties or similar in the Ghidra installation). Look for JDBC connection strings. Check if the url parameter contains 'postgresql' rather than 'derby' or 'hsqldb'.
    Affected if PostgreSQL is the active database backend (Derby and HSQLDB are not affected by this vulnerability)
  3. Verify PostgreSQL authentication is in use
    Check the PostgreSQL pg_hba.conf file for the Ghidra database. Look for entries allowing 'md5' or 'password' authentication rather than 'trust' or 'ident'. Also check if network connections to port 5432 (default) are permitted.
    Affected if PostgreSQL accepts password-based authentication over the network (the vulnerability is exploitable via PasswordChange network messages)
  4. Review PostgreSQL user configuration
    Connect to the Ghidra PostgreSQL database as a superuser and run: SELECT rolname, rolsuper, rolcanlogin FROM pg_roles ORDER BY rolname;. Check for non-superuser accounts that could receive a crafted username.
    Affected if There exist non-superuser database users who could be exploited via crafted usernames in PasswordChange messages
  5. Check network exposure of Ghidra server
    Review Ghidra server startup scripts for the GHI_PORT or similar network port configuration. Verify if the server is bound to 0.0.0.0 or a non-localhost address. Run 'netstat -anp | grep ghidra' or 'ss -tlnp | grep ghidra' to list listening ports.
    Affected if Ghidra server listens on a network interface accessible to potential attackers (not localhost-only)

You are affected if you run Ghidra 11.0 through 11.x with a PostgreSQL backend that accepts network authentication, and the server is network-accessible to untrusted users who can send PasswordChange messages.

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 12.1 or later
Fixed in 12.1
Interim mitigation

Upgrade to Ghidra 12.1 or later to obtain the patched version. As a defense-in-depth measure, implement proper input validation and use parameterized queries instead of string interpolation for all SQL statements.

Recommended fix High confidence

12.1

  1. Back up all Ghidra projects, custom extensions, and user configurations before upgrading
  2. Download Ghidra 12.1 from the official GitHub releases page (github.com/NationalSecurityAgency/ghidra/releases)
  3. Extract the Ghidra 12.1 archive to a new directory (do not overwrite existing installation)
  4. Migrate any custom configurations, user preferences, or extensions from the previous installation to the new version
  5. Verify the installation by running ghidraRun.bat or ghidraRun and checking the version displays 12.1
  6. Test that the PostgresFunctionDatabase functionality works correctly with the new version
Caveat Minor API changes may exist between Ghidra versions; custom extensions or scripts may require testing and potential updates

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

Fix this in Ghidra Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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