Loading vulnerability…
CVE-2026-14669 is a heap-based buffer overflow in PostgreSQL date/time formatting, affecting the timezone-formatting path of to_char(timestamptz). The vulnerable DCH_to_char handling lowercases a timezone string and copies it into a heap-allocated buffer without adequately validating the timezone value's length. A long POSIX timezone abbreviation can overflow that buffer. The corrected implementation bounds the timezone value against the format-item capacity and rejects excessive values with a datetime-value-out-of-range error. PostgreSQL versions before 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a compact authenticated RCE proof-of-concept for CVE-2026-14669 in PostgreSQL's timezone formatting path used by `to_char(timestamptz)`. It contains one primary exploit script (`poc.py`), a Docker lab definition (`docker-compose.yml`), dependency file (`requirements.txt`), and documentation (`README.md`). The exploit is real code, not just detection logic. The Python PoC uses `psycopg` and `pwntools` to speak to PostgreSQL over its normal wire protocol. Its structure is staged: `connect()` establishes a DB session; `leaker()` abuses oversized timezone data and binary `COPY` output from `to_char(now(),'TZ')` to corrupt a varlena length and leak adjacent heap contents, from which it derives the PostgreSQL PIE base using known handler-pointer offsets; `heap_leak()` triggers `to_char(now(),'TZtz')` and parses an `invalid pointer` error message to recover a live heap address; `shaper2()` performs heap shaping and crafts fake memory-context callback structures so that `MemoryContextReset()` eventually calls `system()` with the attacker-controlled command. The default command is `echo PWNED; id`, demonstrating code execution as the postgres service account. The exploit is operational but not broadly portable: it is hardcoded for a specific PostgreSQL 19beta1 official build and image digest, with fixed offsets such as `SYSTEM_PLT`, `RVA_HASH`, `RVA_CMP`, and `ASET_METHODS`. The README claims broader affected versions (14.x through 18.x ranges), but the actual code is tuned to one build and would require retargeting for others. The included Docker Compose file creates a local lab container named `pg-tzlab`, disables autovacuum for heap-grooming stability, and binds PostgreSQL to `127.0.0.1:55432`. Primary exploit capability: authenticated network-based remote code execution against a vulnerable PostgreSQL server, assuming valid credentials and SQL execution ability. Secondary capabilities include memory disclosure of PIE and heap addresses, ASLR bypass assistance, heap grooming, and backend crash/exit during exploitation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL vulnerability referenced by the plugin; no technical vulnerability details are provided.
A PostgreSQL to_char heap-buffer-overflow vulnerability that can execute arbitrary code.
A PostgreSQL to_char heap buffer overflow that can execute arbitrary code.
A PostgreSQL to_char heap buffer overflow that can execute arbitrary code.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.