dbcve.org
GhidraApplication · Nsa

CVE-2026-52754

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 Patch available

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 before 12.1 contains an authentication bypass vulnerability in PKIAuthenticationModule.authenticate() that allows any user with a valid CA-signed certificate to impersonate other users by presenting their public certificate with a null signature. Attackers can escalate privileges, modify repository access controls, exfiltrate shared reverse engineering databases, and permanently compromise server integrity.

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
How this class of weakness works · CWE-347

The application accepts signed data without properly verifying the signature, so an attacker can forge or tamper with content that the system is meant to trust — tokens, updates, licences. Everything built on that trust then becomes unreliable. Remediation is verifying every signature against the correct key and rejecting anything that does not validate.

General guidance for the improper signature verification class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:< 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

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
Vendor patch github.com →
Recommended fix High confidence

Ghidra 12.1

  1. 1. Backup any existing Ghidra installations and custom scripts/extensions
  2. 2. Download Ghidra 12.1 from the official GitHub releases page: https://github.com/NationalSecurityAgency/ghidra/releases/tag/Ghidra_12.1_build
  3. 3. Extract the new Ghidra 12.1 distribution to your desired installation directory
  4. 4. If using Ghidra Server, ensure all clients and the server are upgraded to 12.1 to maintain compatibility
  5. 5. Verify the upgrade by checking Help > About Ghidra shows version 12.1
  6. 6. Test PKI authentication functionality to confirm the vulnerability is remediated
Caveat Major Ghidra upgrades may include API changes that require updates to custom scripts and extensions; review release notes before upgrading production environments

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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