CVE-2026-14663

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-08-13. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct observation of the faulty ciphertext. The OpenSSL version and OpenSSL configuration determine the disabled ciphers. If the application accepts encrypted data as input, decryption will succeed even with the wrong key. This in turn loses the modest protection from the Modification Detection Code (MDC). Affected functions are pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt, pgp_sym_encrypt_bytea, pgp_sym_decrypt_bytea, pgp_pub_encrypt_bytea, and pgp_pub_decrypt_bytea. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

August 29, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
Patch available.
generic

PostgreSQL: CVE-2026-14663: PostgreSQL pgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext

https://www.postgresql.org/support/security/CVE-2026-14663/

Vendor Advisories for CVE-2026-14663(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-10-04ubuntu
redhatpostgresql17-main-17.11-1.hum12026-08-20redhat
redhatpostgresql18-main-18.6-0.1.hum12026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(11 across 7 ecosystems)
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
postgresql18—
  • every version up to 18.5-r0: fixed in 18.5-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
postgresql18—
  • every version up to 18.5-r0: fixed in 18.5-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions)
  • every version up to 15.19-0+deb12u1: fixed in 15.19-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)
  • every version up to 17.11-0+deb13u1: fixed in 17.11-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)
  • every version up to 18.6-1: fixed in 18.6-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 19× in last 7d / 88× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 168 total refreshes for this CVE.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 22:24 UTCVendor advisory
  3. 2026-10-04 22:24 UTCGHSA enrichment
  4. 2026-10-03 19:53 UTCEG score recompute
  5. 2026-10-03 19:53 UTCVendor advisory
  6. 2026-10-03 19:53 UTCGHSA enrichment
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-02 08:05 UTCEG score recompute
  9. 2026-10-02 08:05 UTCVendor advisory
  10. 2026-10-02 08:05 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-09-30 21:50 UTCEG score recompute
  13. 2026-09-30 21:50 UTCVendor advisory
  14. 2026-09-30 21:50 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-29 15:20 UTCEPSS rescore
  17. 2026-09-29 07:19 UTCEG score recompute
  18. 2026-09-29 07:19 UTCVendor advisory
  19. 2026-09-29 07:19 UTCGHSA enrichment
  20. 2026-09-28 08:32 UTCVendor advisory
  21. 2026-09-28 08:32 UTCGHSA enrichment
  22. 2026-09-27 09:48 UTCEG score recompute
  23. 2026-09-27 09:48 UTCVendor advisory
  24. 2026-09-27 09:48 UTCGHSA enrichment
  25. 2026-09-26 15:58 UTCEPSS rescore
Show 75 more
  1. 2026-09-25 03:37 UTCEG score recompute
  2. 2026-09-25 03:37 UTCVendor advisory
  3. 2026-09-25 03:37 UTCGHSA enrichment
  4. 2026-09-23 20:51 UTCVendor advisory
  5. 2026-09-23 20:51 UTCGHSA enrichment
  6. 2026-09-22 21:03 UTCEG score recompute
  7. 2026-09-22 21:03 UTCVendor advisory
  8. 2026-09-22 21:03 UTCGHSA enrichment
  9. 2026-09-21 19:58 UTCVendor advisory
  10. 2026-09-21 19:58 UTCGHSA enrichment
  11. 2026-09-20 20:19 UTCVendor advisory
  12. 2026-09-20 20:19 UTCGHSA enrichment
  13. 2026-09-19 21:42 UTCVendor advisory
  14. 2026-09-19 21:42 UTCGHSA enrichment
  15. 2026-09-18 23:06 UTCEG score recompute
  16. 2026-09-18 23:06 UTCVendor advisory
  17. 2026-09-18 23:06 UTCGHSA enrichment
  18. 2026-09-18 19:27 UTCEPSS rescore
  19. 2026-09-18 00:30 UTCEG score recompute
  20. 2026-09-18 00:30 UTCVendor advisory
  21. 2026-09-18 00:30 UTCGHSA enrichment
  22. 2026-09-17 00:12 UTCEG score recompute
  23. 2026-09-17 00:12 UTCVendor advisory
  24. 2026-09-17 00:11 UTCGHSA enrichment
  25. 2026-09-16 14:07 UTCEPSS rescore
  26. 2026-09-16 05:14 UTCEPSS rescore
  27. 2026-09-15 20:11 UTCEG score recompute
  28. 2026-09-15 20:11 UTCVendor advisory
  29. 2026-09-15 20:11 UTCGHSA enrichment
  30. 2026-09-14 20:53 UTCVendor advisory
  31. 2026-09-14 20:53 UTCGHSA enrichment
  32. 2026-09-13 22:08 UTCVendor advisory
  33. 2026-09-13 22:08 UTCGHSA enrichment
  34. 2026-09-12 23:32 UTCEG score recompute
  35. 2026-09-12 23:32 UTCVendor advisory
  36. 2026-09-12 23:32 UTCGHSA enrichment
  37. 2026-09-12 15:00 UTCEPSS rescore
  38. 2026-09-12 00:56 UTCEG score recompute
  39. 2026-09-12 00:56 UTCVendor advisory
  40. 2026-09-12 00:56 UTCGHSA enrichment
  41. 2026-09-11 14:52 UTCEPSS rescore
  42. 2026-09-11 09:36 UTCEPSS rescore
  43. 2026-09-11 02:20 UTCEG score recompute
  44. 2026-09-11 02:20 UTCVendor advisory
  45. 2026-09-11 02:20 UTCGHSA enrichment
  46. 2026-09-10 09:34 UTCEPSS rescore
  47. 2026-09-10 03:44 UTCVendor advisory
  48. 2026-09-10 03:44 UTCGHSA enrichment
  49. 2026-09-09 05:06 UTCEG score recompute
  50. 2026-09-09 05:06 UTCVendor advisory
  51. 2026-09-09 05:06 UTCGHSA enrichment
  52. 2026-09-08 22:00 UTCEPSS rescore
  53. 2026-09-07 20:32 UTCEG score recompute
  54. 2026-09-07 20:32 UTCVendor advisory
  55. 2026-09-07 20:32 UTCGHSA enrichment
  56. 2026-09-07 16:01 UTCEPSS rescore
  57. 2026-09-06 21:56 UTCEG score recompute
  58. 2026-09-06 21:56 UTCVendor advisory
  59. 2026-09-06 21:56 UTCGHSA enrichment
  60. 2026-09-06 13:47 UTCEPSS rescore
  61. 2026-09-05 23:13 UTCEG score recompute
  62. 2026-09-05 23:13 UTCVendor advisory
  63. 2026-09-05 23:13 UTCGHSA enrichment
  64. 2026-09-05 00:37 UTCEG score recompute
  65. 2026-09-05 00:37 UTCVendor advisory
  66. 2026-09-05 00:36 UTCGHSA enrichment
  67. 2026-09-04 05:06 UTCEPSS rescore
  68. 2026-09-03 23:13 UTCVendor advisory
  69. 2026-09-03 23:13 UTCGHSA enrichment
  70. 2026-09-02 23:20 UTCVendor advisory
  71. 2026-09-02 23:20 UTCGHSA enrichment
  72. 2026-09-01 20:18 UTCEG score recompute
  73. 2026-09-01 20:18 UTCVendor advisory
  74. 2026-09-01 20:18 UTCGHSA enrichment
  75. 2026-09-01 13:53 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-14663?
CVE-2026-14663 is a medium vulnerability published on August 13, 2026. Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct observation of the faulty ciphertext. The OpenSSL version and OpenSSL configuration determine the disabled ciphers. If the application accepts encrypted data as input, decryption will succeed…
When was CVE-2026-14663 disclosed?
CVE-2026-14663 was first published on August 13, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14663 actively exploited?
CVE-2026-14663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14663?
CVE-2026-14663 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14663?
A fix for CVE-2026-14663 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-14663 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14663

Explore →

Is Your Infrastructure Affected by CVE-2026-14663?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs