CVE-2026-6474

PostgreSQL timeofday() can disclose portions of server memory

MEDIUM
4.3
CVSS Score
Published: May 14, 2026 at 01:00 PM UTC
Updated: June 17, 2026 at 11:00 AM UTC
1 product affected across 1 vendorPostgreSQL

Using PostgreSQL by N/A?

Get instant alerts when new vulnerabilities affect PostgreSQL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server memory, via crafted timezone zones. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 14.2315 ≤ v < 15.1815.0 ≤ v < 15.1816 ≤ v < 16.1416.0 ≤ v < 16.1417 ≤ v < 17.1017.0 ≤ v < 17.1018 ≤ v < 18.418.0 ≤ v < 18.415161718
Affected range stops below 14.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMPostgreSQL
Vector?

Quick Info

StatusANALYZED
CWE
CWE-134

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card