CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HCVE-2026-14661 PostgreSQL dblink and subscriptions can append to arbitrary files
High (8.1). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
External control of file name in PostgreSQL dblink and CREATE/ALTER SUBSCRIPTION allows a user to achieve persistent denial of service, via appending invalid data to a chosen file. Specifically, the "sslkeylogfile" connection parameter appends data, in NSS keylog format, to a file of the user's choosing. This "sslkeylogfile" mechanism cannot add arbitrary bytes. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are also affected if libpq version 18 or later is installed and in use by the server.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-73 External Control of File Name or Path
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- Assigned by
- PostgreSQL (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-14661 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-14661?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-14661?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-14661 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-14661)
HTML:
<a href="https://cve.bz/cve/CVE-2026-14661"><img src="https://cve.bz/cve/badge/CVE-2026-14661.svg" alt="CVE-2026-14661"></a>
Fix and patched versions
- Debian, Red Hat, Alpine: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | postgresql-15 | no fix listed | DEBIAN-CVE-2026-14661 |
| Debian | 13 | postgresql-17 | 17.12-0+deb13u1 | DEBIAN-CVE-2026-14661 |
| Debian | 14 | postgresql-18 | no fix listed | DEBIAN-CVE-2026-14661 |
| Ubuntu | 20.04:LTS | postgresql-12 | no fix listed | UBUNTU-CVE-2026-14661 |
| Ubuntu | 22.04:LTS | postgresql-14 | no fix listed | UBUNTU-CVE-2026-14661 |
| Ubuntu | 24.04:LTS | postgresql-16 | no fix listed | UBUNTU-CVE-2026-14661 |
| Ubuntu | 26.04:LTS, 26.10 | postgresql-18 | no fix listed | UBUNTU-CVE-2026-14661 |
| Ubuntu | Pro:14.04:LTS | postgresql-9.3 | no fix listed | UBUNTU-CVE-2026-14661 |
| Ubuntu | Pro:16.04:LTS | postgresql-9.5 | no fix listed | UBUNTU-CVE-2026-14661 |
| Ubuntu | Pro:18.04:LTS | postgresql-10 | no fix listed | UBUNTU-CVE-2026-14661 |
| Red Hat | hummingbird:1 | libpq, libpq-devel | 0:18.7-0.1.hum1 | RHSA-2026:99821 |
| Alpine | v3.21, v3.22 | postgresql15 | 15.20-r0 | ALPINE-CVE-2026-14661 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql16 | 16.16-r0 | ALPINE-CVE-2026-14661 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql17 | 17.12-r0 | ALPINE-CVE-2026-14661 |
| Alpine | v3.23, v3.24 | postgresql18 | 18.7-r0 | ALPINE-CVE-2026-14661 |
| Azure Linux | 3 | postgresql | no fix listed | AZL-113789 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.
Red Hat
Red Hat rates this Important.
Red Hat rates this vulnerability as having an Important severity because authenticated users with access to connection-string-capable database mechanisms can corrupt essential service files, resulting in a persistent and severe denial of service. Under default Red Hat Enterprise Linux deployments, SELinux policy confines the database daemon and prevents file modifications outside of PostgreSQL-managed directories, protecting core operating system components. Nonetheless, invalid TLS key logging data appended to internal database configuration files or data clusters can permanently crash the service and prevent startup, necessitating manual administrative recovery.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | libpq | Affected | |
| Red Hat Hardened Images | postgresql17 | Affected | |
| Red Hat Hardened Images | postgresql18 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-14661.
Attack patterns (CAPEC)
- CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
- CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
- CAPEC-72 URL Encoding Likelihood: High · Severity: High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
- CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
- CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
- CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.