<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dnssec on CuraSec</title><link>https://curasec.metacog.co.kr/tags/dnssec/</link><description>Recent content in Dnssec on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 17 Sep 2026 15:32:45 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/dnssec/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical Unbound DNS RCE via Malicious DNSSEC Zone (CVE-2026-81642)</title><link>https://curasec.metacog.co.kr/insights/2026-09-17-critical-unbound-dnssec-validator-flaw-could-allow-rce-via-a/</link><pubDate>Thu, 17 Sep 2026 15:32:45 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-17-critical-unbound-dnssec-validator-flaw-could-allow-rce-via-a/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> A public PoC exists for this critical heap overflow enabling RCE against any Unbound resolver that validates DNSSEC; patch to Unbound 1.26.1 immediately and verify all resolver deployments (containers, host-based, service mesh sidecars) are updated.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or IOCs reported, and EPSS is 0.01; the attack path (attacker-controlled zone triggers RCE in resolver) is worth noting for future hunt hypotheses, but no detection work is warranted until exploitation evidence emerges.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-81642 — CISA KEV: not listed, EPSS 0.01, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>