Loading vulnerability…
CVE-2026-14663 is a cleartext-storage vulnerability in PostgreSQL's pgcrypto PGP encryption and decryption functions when an application selects a cipher disabled by the installed OpenSSL version or its local cryptographic policy. Instead of reporting an error, affected pgcrypto code can silently encrypt plaintext as cleartext and decrypt that cleartext successfully. Affected functions include the text and bytea variants of pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, and pgp_pub_decrypt. PostgreSQL versions before 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL vulnerability referenced by the plugin; no technical vulnerability details are provided.
A PostgreSQL pgcrypto flaw in which OpenSSL-disabled ciphers can silently produce or consume cleartext.
A pgcrypto flaw where ciphers disabled in OpenSSL may silently encrypt to and decrypt from cleartext.
A pgcrypto flaw in which ciphers disabled in OpenSSL may silently encrypt and decrypt as cleartext.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.