CVE-2020-25696: A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 85.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: postgres-decoderbufs (AlmaLinux:8) 0.10.0-2.module_el8.6.0+2758+4f4474df, 0.10.0-2.module_el8.6.0+2760+1746ec94; postgresql (Alpine:v3.10) 11.10-r0; postgresql (Alpine:v3.11) 12.5-r0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to postgres-decoderbufs (AlmaLinux:8) 0.10.0-2.module_el8.6.0+2758+4f4474df, 0.10.0-2.module_el8.6.0+2760+1746ec94; postgresql (Alpine:v3.10) 11.10-r0; postgresql (Alpine:v3.11) 12.5-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code as the operating system account running psql. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
- BDU:2020-05466
- ALSA-2020:5620
- DLA-2478-1
- openSUSE-SU-2020:2018-1
- openSUSE-SU-2020:2019-1
- openSUSE-SU-2020:2028-1
- openSUSE-SU-2020:2029-1
- openSUSE-SU-2021:0337-1
- openSUSE-SU-2024:11184-1
- openSUSE-SU-2024:11185-1
- openSUSE-SU-2024:11186-1
- openSUSE-SU-2024:11187-1
- openSUSE-SU-2024:12387-1
- openSUSE-SU-2024:13243-1
- openSUSE-SU-2024:14360-1
- openSUSE-SU-2025:15580-1
- RHSA-2020:5316
- RHSA-2020:5317
- RHSA-2020:5401
- RHSA-2020:5567
- Published
- Nov 23, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-183
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Is PostgreSQL on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql9.5.0 and later · before 9.5.24
- postgresql postgresql9.6.0 and later · before 9.6.20
- postgresql postgresql10.0 and later · before 10.15
- postgresql postgresql11.0 and later · before 11.10
- postgresql postgresql12.0 and later · before 12.5
- postgresql postgresql13.0 and later · before 13.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a PostgreSQL
- All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | postgres-decoderbufs | before 0.10.0-2.module_el8.6.0+2758+4f4474df | 0.10.0-2.module_el8.6.0+2758+4f4474df |
| AlmaLinux:8 | postgres-decoderbufs | before 0.10.0-2.module_el8.6.0+2760+1746ec94 | 0.10.0-2.module_el8.6.0+2760+1746ec94 |
| Alpine:v3.10 | postgresql | from 9.5.0 · before 11.10-r0 | 11.10-r0 |
| Alpine:v3.11 | postgresql | from 9.5.0 · before 12.5-r0 | 12.5-r0 |
| Alpine:v3.15 | postgresql12 | before 12.5-r0 | 12.5-r0 |
| Alpine:v3.15 | postgresql14 | before 12.5-r0 | 12.5-r0 |
| Alpine:v3.17 | postgresql15 | before 12.5-r0 | 12.5-r0 |
| Debian:11 | postgresql-13 | before 13.1-1 | 13.1-1 |
| Debian:9 | postgresql-9.6 | before 9.6.20-0+deb9u1 | 9.6.20-0+deb9u1 |
| openSUSE:Leap 15.1 | postgresql10 | before 10.15-lp151.2.21.1 | 10.15-lp151.2.21.1 |
| openSUSE:Leap 15.1 | postgresql12 | before 12.5-lp151.10.1 | 12.5-lp151.10.1 |
| openSUSE:Leap 15.2 | postgresql | before 13-lp152.3.6.1 | 13-lp152.3.6.1 |
| openSUSE:Leap 15.2 | postgresql10 | before 10.15-lp152.2.9.1 | 10.15-lp152.2.9.1 |
| openSUSE:Leap 15.2 | postgresql12 | before 12.5-lp152.3.10.1 | 12.5-lp152.3.10.1 |
| openSUSE:Tumbleweed | postgresql10 | before 10.18-1.3 | 10.18-1.3 |
| openSUSE:Tumbleweed | postgresql11 | before 11.13-1.3 | 11.13-1.3 |
| openSUSE:Tumbleweed | postgresql12 | before 12.8-1.3 | 12.8-1.3 |
| openSUSE:Tumbleweed | postgresql13 | before 13.4-1.3 | 13.4-1.3 |
| openSUSE:Tumbleweed | postgresql14 | before 14.5-2.1 | 14.5-2.1 |
| openSUSE:Tumbleweed | postgresql15 | before 15.4-2.1 | 15.4-2.1 |
| openSUSE:Tumbleweed | postgresql16 | before 16.4-1.1 | 16.4-1.1 |
| openSUSE:Tumbleweed | postgresql17 | before 17.6-2.1 | 17.6-2.1 |
| Red Hat:enterprise_linux:8::appstream | libpq | before 0:12.5-1.el8_3 | 0:12.5-1.el8_3 |
| Red Hat:enterprise_linux:8::appstream | libpq-debuginfo | before 0:12.5-1.el8_3 | 0:12.5-1.el8_3 |
+96
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to 55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-10733Sep 16, 2020 · The Windows installer for PostgreSQL 9.5 - 12 invokes system-provided executables that do not have fully-qualified paths.29Monitor
- ← EarlierCVE-2020-25694Nov 15, 2020 · A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.32Monitor
- Later →CVE-2021-20229Feb 23, 2021 · A flaw was found in PostgreSQL in versions before 13.2.17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:postgres-decoderbufs | 0.10.0-2.module_el8.6.0+2760+1746ec94 · AlmaLinux:8 | Package registry (OSV) |
| alpine:postgresql | 11.10-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:postgresql12 | 12.5-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:postgresql14 | 12.5-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:postgresql15 | 12.5-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:postgresql-13 | 13.1-1 · Debian:11 | Package registry (OSV) |
| debian:postgresql-9.6 | 9.6.20-0+deb9u1 · Debian:9 | Package registry (OSV) |
| opensuse:postgresql | 13-lp152.3.6.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:postgresql10 | 10.15-lp152.2.9.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:postgresql11 | 11.13-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql12 | 12.5-lp152.3.10.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:postgresql13 | 13.4-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql14 | 14.5-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql15 | 15.4-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql16 | 16.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql17 | 17.6-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-contrib | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-contrib-syspaths | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-debuginfo | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-devel | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-docs | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-libs | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-plperl | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-plpython | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-pltcl | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-server | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-server-syspaths | 0:10.15-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| rocky linux:pgaudit | 0:1.4.0-4.module+el8.4.0+545+ca56da2e · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:postgres-decoderbufs | 0:0.10.0-2.module+el8.5.0+684+c3892ef9 · Rocky Linux:8 | Package registry (OSV) |
+5
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-967 · Nov 18, 2020(Postgresql Sunucu Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-183 · Permissive List of Allowed InputsCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Double EncodingCAPEC-120likelihood: Low · Medium
- Using Leading 'Ghost' Character Sequences to Bypass Input FiltersCAPEC-3likelihood: Medium · Medium
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Using Unicode Encoding to Bypass Validation LogicCAPEC-71likelihood: Medium · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.