USN-6104-1: postgresql-10 Ubuntu
CVSS: UnknownPublished
Published 24-05-2023Last modified 27-04-2026
Vulnerability summary
USN-6104-1 is a vulnerability in postgresql-10 Ubuntu with no CVSS score yet.
CVSS score
Not scored
010
No CVSS score recordedEPSS score
Not scored
0%100%
No EPSS score yetKEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded
Advisory lineage
Upstream 2 · Downstream 0 · Related 2Timeline
- 24-05-2023PublishedVulnerability first disclosed.
- 27-04-2026Last modifiedVulnerability information updated.
Description
postgresql-10, postgresql-12, postgresql-14, postgresql-15 vulnerabilities Alexander Lakhin discovered that PostgreSQL incorrectly handled certain CREATE privileges. An authenticated user could possibly use this issue to execute arbitrary code as the bootstrap supervisor. (CVE-2023-2454) Wolfgang Walther discovered that PostgreSQL incorrectly handled certain row security policies. An authenticated user could possibly use this issue to complete otherwise forbidden reads and modifications. (CVE-2023-2455)
CVSS metrics
Risk metrics not yet published.
EPSS trend
No EPSS score has been published for this record yet.
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Ubuntu3 products
- postgresql-10< 10.23-0ubuntu0.18.04.2
- postgresql-12< 12.15-0ubuntu0.20.04.1
- postgresql-14< 14.8-0ubuntu0.22.04.1
1 vendor · 3 products
References
3 linksRelated vulnerabilities
USN-8653-1ubuntupostgresql-14+2postgresql-14, postgresql-16, postgresql-18 vulnerabilities
It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when
an early failure occurred. An authenticated user could possibly use this
issue to execute arbitrary SQL commands. (CVE-2026-6464)
It was discovered that PostgreSQL incorrectly reset extended statistics
ownership during ALTER TABLE ALTER TYPE operations. An attacker could
possibly use this issue to obtain sensitive information or gain unintended
privileges. (CVE-2026-6469)
It was discovered that PostgreSQL failed to check the USAGE privilege on
types. An authenticated user could possibly use this issue to obtain
sensitive information. (CVE-2026-6470)
It was discovered that PostgreSQL logical decoding could load arbitrary
shared libraries. An authenticated user could possibly use this issue to
execute arbitrary code. (CVE-2026-6471)
It was discovered that PostgreSQL had integer wraparound issues in tsvector
and tsquery allocations. An authenticated user could possibly use this
issue to execute arbitrary code. (CVE-2026-14662)
It was discovered that PostgreSQL pgcrypto silently used cleartext when
OpenSSL-disabled ciphers were requested. An authenticated user could
possibly use this issue to obtain sensitive information. (CVE-2026-14663)
It was discovered that PostgreSQL had a heap buffer overflow in regular
expression processing. An authenticated user could possibly use this issue
to execute arbitrary code. (CVE-2026-14664)
It was discovered that PostgreSQL row security policies were not properly
invalidated when roles were modified. An attacker could possibly use this
issue to bypass intended row security restrictions. (CVE-2026-14666)
It was discovered that PostgreSQL had a type confusion issue in the
selectivity estimator involving ctid. An authenticated user could possibly
use this issue to obtain sensitive information. (CVE-2026-14668)
It was discovered that PostgreSQL had a heap buffer overflow in the to_char
function. An authenticated user could possibly use this issue to execute
arbitrary code. (CVE-2026-14669)
It was discovered that PostgreSQL had a heap buffer overflow in the PL/Perl
tied object handling. An authenticated user could possibly use this issue
to execute arbitrary code. (CVE-2026-14670)
It was discovered that PostgreSQL had a type confusion issue in the
referential integrity plan cache. An authenticated user could possibly use
this issue to execute arbitrary code. (CVE-2026-14671)
It was discovered that PostgreSQL had an observable response discrepancy
when non-default scram_iterations were used. A remote attacker could
possibly use this issue to enumerate valid usernames. This issue only
affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-14672)
It was discovered that PostgreSQL amcheck did not clear untrusted search
paths. An authenticated user could possibly use this issue to execute
arbitrary code. (CVE-2026-14673)
It was discovered that PostgreSQL had a heap buffer overflow in
pg_stat_statements. An authenticated user could possibly use this issue to
execute arbitrary code. This issue only affected Ubuntu 26.04 LTS.
(CVE-2026-14676)
It was discovered that PostgreSQL had integer wraparound issues in PL/Tcl
and PL/Perl allocations on 32-bit systems. An authenticated user could
possibly use this issue to execute arbitrary code. (CVE-2026-14677)
It was discovered that PostgreSQL pg_trgm read past the end of a buffer
during picksplit operations. An authenticated user could possibly use this
issue to obtain sensitive information. (CVE-2026-14678)
It was discovered that PostgreSQL had a stack buffer overflow in argument
matching. An authenticated user could possibly use this issue to corrupt
server memory. (CVE-2026-14679)
It was discovered that PostgreSQL had a type confusion issue when functions
used internal arguments. An authenticated user could possibly use this
issue to execute arbitrary code. (CVE-2026-14680)
It was discovered that PostgreSQL did not properly enforce GSSAPI
encryption when used together with SSL. An attacker could possibly use this
issue to perform a machine-in-the-middle attack and obtain sensitive
information. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-14681)
It was discovered that PostgreSQL allowed SQL injection through EXTRACT
arguments during expression deparsing. An authenticated user could possibly
use this issue to perform SQL injection attacks. (CVE-2026-15741)
It was discovered that PostgreSQL fuzzystrmatch had integer wraparound
issues that could write to arbitrary addresses. An authenticated user could
possibly use this issue to execute arbitrary code. (CVE-2026-15742)
It was discovered that PostgreSQL had a type confusion issue in
pg_restore_attribute_stats(). An authenticated user could possibly use this
issue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS.
(CVE-2026-16238)
It was discovered that PostgreSQL had a type confusion issue when handling
cursor CLOSE and DECLARE operations. An authenticated user could possibly
use this issue to execute arbitrary code. (CVE-2026-16239)
It was discovered that PostgreSQL had an integer underflow in the ECPG
client library. An attacker could possibly use this issue to cause
PostgreSQL to crash, resulting in a denial of service. (CVE-2026-16241)
It was discovered that PostgreSQL had an out-of-bounds read in the ascii()
function. An authenticated user could possibly use this issue to obtain
sensitive information. (CVE-2026-18024)
It was discovered that the psql \unrestrict command allowed the superuser
of a pg_dump origin server to execute arbitrary code in the psql client. An
attacker could possibly use this issue to execute arbitrary code.
(CVE-2026-18408)
It was discovered that PostgreSQL pg_dump had a heap buffer overflow. An
attacker could possibly use this issue to execute arbitrary code.
(CVE-2026-19385)USN-8294-1ubuntupostgresql-14+3postgresql-14, postgresql-16, postgresql-17, postgresql-18 vulnerabilities
It was discovered that PostgreSQL did not correctly enforce authorization
for CREATE TYPE. An attacker could possibly use this issue to execute
arbitrary SQL functions. (CVE-2026-6472)
It was discovered that PostgreSQL incorrectly handled large user input in
multiple server features. An attacker could possibly use this issue to
cause PostgreSQL to crash, resulting in a denial of service, or execute
arbitrary code. (CVE-2026-6473)
It was discovered that PostgreSQL incorrectly handled format strings in
the timeofday() function. An attacker could possibly use this issue to
obtain sensitive information. (CVE-2026-6474)
It was discovered that PostgreSQL incorrectly followed symbolic links in
pg_basebackup and pg_rewind. An attacker could possibly use this issue to
overwrite local files and execute arbitrary code. (CVE-2026-6475)
It was discovered that PostgreSQL had an SQL injection vulnerability in
pg_createsubscriber. An attacker could possibly use this issue to execute
arbitrary SQL as a superuser. This issue only affected Ubuntu 25.10 and
Ubuntu 26.04 LTS. (CVE-2026-6476)
It was discovered that PostgreSQL used an unsafe libpq function in large
object operations. An attacker could possibly use this issue to overwrite
client memory and execute arbitrary code. (CVE-2026-6477)
It was discovered that PostgreSQL did not compare MD5-hashed passwords in
constant time. An attacker could possibly use this issue to obtain
sensitive information. (CVE-2026-6478)
It was discovered that PostgreSQL had uncontrolled recursion during SSL and
GSS negotiation. An attacker could possibly use this issue to cause a
denial of service. (CVE-2026-6479)
It was discovered that PostgreSQL incorrectly handled array length
mismatches in pg_restore_attribute_stats(). An attacker could possibly use
this issue to obtain sensitive information. This issue only affected Ubuntu
26.04 LTS. (CVE-2026-6575)
It was discovered that PostgreSQL had a stack buffer overflow in the refint
module. An attacker could use this issue to cause PostgreSQL to crash,
resulting in a denial of service, or possibly execute arbitrary code.
(CVE-2026-6637)
It was discovered that PostgreSQL had an SQL injection vulnerability in
logical replication REFRESH PUBLICATION. An attacker could possibly use
this issue to execute arbitrary SQL. This issue only affected Ubuntu 24.04
LTS, Ubuntu 25.10, and Ubuntu 26.04 LTS. (CVE-2026-6638)USN-8072-1ubuntupostgresql-14+2postgresql-14, postgresql-16, postgresql-17 vulnerabilities
Altan Birler discovered that PostgreSQL incorrectly validated oidvector
types. An attacker could possibly use this issue to obtain a few bytes of
sensitive information. (CVE-2026-2003)
Daniel Firer discovered that PostgreSQL incorrectly validated input in the
intarray extension. An attacker could possibly use this issue to execute
arbitrary code. (CVE-2026-2004)
It was dicovered that PosgreSQL incorrectly handled certain pgcrypto memory
operations. An attacker could possibly use this issue to execute arbitrary
code. (CVE-2026-2005)
Paul Gerste and Moritz Sanft discovered that PostgreSQL incorrectly
validated multibyte character lengths. An attacker could possibly use this
issue to execute arbitrary code. (CVE-2026-2006)USN-7908-1ubuntupostgresql-14+2postgresql-14, postgresql-16, postgresql-17 vulnerabilities
Jelte Fennema-Nio discovered that the PostgreSQL CREATE STATISTICS command
did not correctly check for schema CREATE privileges. An authenticated
attacker could possibly use this issue to create a denial of service
against other CREATE STATISTICS users. (CVE-2025-12817)
Aleksey Solovev discovered that the PostgreSQL libpq client library
incorrectly handled certain memory operations. A remote attacker could
possibly use this issue to cause libpq to crash, resulting in a denial of
service. (CVE-2025-12818)USN-7741-1ubuntupostgresql-14+1postgresql-14, postgresql-16, postgresql-17 vulnerabilities
Dean Rasheed discovered that PostgreSQL incorrectly handled access control
lists. An attacker could possibly use this issue to obtain sensitive
information. (CVE-2025-8713)
Martin Rakhmanov, Matthieu Denais, and RyotaK discovered that the PostgreSQL
pg_dump utility allowed untrusted data inclusion. A malicious superuser
could use this issue to execute arbitrary code when a dump script is
reloaded. (CVE-2025-8714)
Noah Misch discovered that the PostgreSQL pg_dump utility incorrectly
filtered line breaks in object names. An attacker could create object names
that execute arbitrary SQL commands when a dump script is reloaded.
(CVE-2025-8715)USN-7132-1ubuntupostgresql-12+2postgresql-12, postgresql-14, postgresql-16 vulnerabilities
It was discovered that PostgreSQL incorrectly tracked tables with row
security. A remote attacker could possibly use this issue to perform
forbidden reads and modifications. (CVE-2024-10976)
Jacob Champion discovered that PostgreSQL clients used untrusted server
error messages. An attacker that is able to intercept network
communications could possibly use this issue to inject error messages that
could be interpreted as valid query results. (CVE-2024-10977)
Tom Lane discovered that PostgreSQL incorrectly handled certain privilege
assignments. A remote attacker could possibly use this issue to view or
change different rows from those intended. (CVE-2024-10978)
Coby Abrams discovered that PostgreSQL incorrectly handled environment
variables. A remote attacker could possibly use this issue to execute
arbitrary code. (CVE-2024-10979)