All reports
High

External Secrets Operator has DNS-based secret exfiltration via getHostByName in External Secrets v2 template engine

Affected versions

Version ranges need review.

Affected versions
<1.3.3-0.20260331202714-6800989bdc12
Fixed version
1.3.3-0.20260331202714-6800989bdc12
Affected versions
< 1.3.3-0.20260331202714-6800989bdc12
Fixed version
1.3.3-0.20260331202714-6800989bdc12
Affected versions
>= 2.0.0, <= 2.2.0
Fixed version
Not reported

Exploitation

CVE-2026-34984

Probability of exploitation in the next 30 days: 0.27%

FIRST EPSS · 2026-11-20

Description

Summary

The v2 template engine in runtime/template/v2/template.go imports Sprig’s TxtFuncMap() and removes env and expandenv, but leaves getHostByName available to user-controlled templates. Because ESO executes templates inside the controller process, an attacker who can create or update templated ExternalSecret resources can trigger controller-side DNS lookups using secret-derived values, creating a DNS exfiltration primitive.

Impact

This is a confidentiality issue. In environments where untrusted or lower-trust users can author templated ExternalSecret resources and the controller can perform DNS resolution, fetched secret material can be exfiltrated through DNS without requiring direct outbound access from the attacker’s workload.

Links

Credits

  • kodareef5