CVE-2026-49498
SQL injection in Ghidra password-change flow enables DB compromise.
WAF coverage: SQL injection. Signatures match well at the request layer.
Also consider: parameterized queries · ORM
Is CVE-2026-49498 being exploited?
Not confirmed. CVE-2026-49498 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-49498?
CVE-2026-49498 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-49498?
Yes. A fix has been recorded for CVE-2026-49498. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49498 affect?
CVE-2026-49498 affects Ghidra 11.0 (before 12.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49498?
Upgrade to 12.1+; verify no unauthorized access after update.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated SQL injection via crafted username in PasswordChange can run arbitrary SQL, escalating to PostgreSQL SUPERUSER and full DB control.
Patch when possible
- affected>= 11.0 and < 12.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.