22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
discuss
- Points171
- Comments31
discuss
Story details from Hacker News ↗ · linked article on mehmetince.net.
22-Year-Old PostgreSQL Bug Turned into Remote Code Execution was first seen on Hacker News · Front page on Nov 12, 2026. Since then it has appeared in 84 checks on 2 different days. Its best position was #7 of 30, reached on Nov 12, 21:13 UTC. It dropped off the list after Nov 13, 15:58 UTC. The same link also trended on Lobsters, which raises its cross-platform score.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Hacker News · Front page | #7 | 2 | 84 | |
| LLobsters · Hottest How I Ended Up Turning a 22-Year-Old PostgreSQL Type-Confusion… | same link | |||
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
Correct me if I'm wrong, but those all look like sql exploits. Don't those already require some sort of authenticated remote access. They are security issues, but calling them remote code exploitation make them seem more dangerous than they are. These seem more like privilege escalation, you have access through a…
Long, meandering article, mixed human/AI writing probably, but the exploit is neat: Create a prepared statement on a table, change the table, then run the prepared statement (which should have been updated but wasn't).
I would call this more of a privilege escalation attack than RCE.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 13, 15:58 UTC, after 2 days of trending.
#7 on Hacker News · Front page, on Nov 12, 21:13 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 12, 2026 and has been on the list on 2 days (84 checks) since.
171 points and 31 comments; submitted by ozirus on Nov 12, 2026.