CVE-2026-14661
PostgreSQL dblink and subscriptions can append to arbitrary files
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.
Fixes and workarounds
Workaround
Revoke public EXECUTE permission on dblink functions Revoke pg_create_subscription from any roles that do not already have pg_write_server_files privileges
Source: CNA: PostgreSQLAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| PostgreSQL n/a |
≥ 18; < 18.7 (affected, rpm) ≥ 17; < 17.12 (affected, rpm) ≥ 16; < 16.16 (affected, rpm) ≥ 15; < 15.20 (affected, rpm) ≥ 0; < 14.25 (affected, rpm) Other versions: unaffected |
CNA: PostgreSQL |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | CNA: PostgreSQL |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.postgresql.org/support/security/CVE-2026-14661/CNA: PostgreSQL
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.