<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgresql on CuraSec</title><link>https://curasec.metacog.co.kr/tags/postgresql/</link><description>Recent content in Postgresql on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 05 Sep 2026 13:51:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>PostgreSQL CVE-2026-6471: Replication Role Enables OS Code Execution</title><link>https://curasec.metacog.co.kr/insights/2026-09-05-postgresql-fixes-12-year-old-logical-decoding-flaw-enabling/</link><pubDate>Sat, 05 Sep 2026 13:51:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-05-postgresql-fixes-12-year-old-logical-decoding-flaw-enabling/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> A public PoC exists but EPSS is near zero and it is not KEV-listed; exploitation requires REPLICATION attribute (a non-default privilege), so immediate fire-drill pressure is low. Patch PostgreSQL to 18.6, 17.11, 16.15, 15.19, or 14.24, and audit which accounts hold the REPLICATION attribute in your instances.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation is reported and no IOCs are available; the public PoC is useful context for understanding how a compromised REPLICATION account could achieve OS-level execution, informing future detection logic around abnormal logical decoding activity, but no immediate hunt is warranted.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-6471 — CISA KEV: not listed, EPSS 0.00, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>