PostgreSQL: Improper Neutralization of CRLF Sequences
CVE-2025-8715 is a high-severity improper neutralization of CRLF sequences vulnerability in PostgreSQL, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 17.6, 16.10, 15.14 as the first without the flaw, so updating PostgreSQL to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update PostgreSQL to 17.6 or 16.10 or 15.14 or 14.19, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| PostgreSQL | PostgreSQL | 17 up to, but not including, 17.6; 16 up to, but not including, 16.10; 15 up to, but not including, 15.14; 14 up to, but not including, 14.19; 11.20 up to, but not including, 13.22 | 17.6, 16.10, 15.14, 14.19, 13.22 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
Improper neutralization of newlines in pg_dump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks can achieve SQL injection as a superuser of the restore target server. pg_dumpall, pg_restore, and pg_upgrade are also affected. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected. Versions before 11.20 are unaffected. CVE-2012-0868 had fixed this class of problem, but version 11.20 reintroduced it.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of CRLF Sequences
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
How developers prevent this class of flaw
- Appropriately filter or quote CRLF sequences in user-controlled input.
More Improper Neutralization of CRLF Sequences vulnerabilities (CWE-93)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in PostgreSQL
- 7.2 High severity
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
- 7.2 High severity
- 8.8 High severity
Recent Improper Neutralization of CRLF Sequences vulnerabilities
- 7.2 High severity
- 8.7 High severity
- 7.7 High severity
- 9.3 Critical severity
- 7.1 High severity
- 7.5 High severity
Spotted an error? Tell us.