CVE-2026-47701 affects the OpenTelemetry Operator for Kubernetes. The TargetAllocator component improperly preserves Prometheus Operator ServiceMonitor file-based authentication and TLS settings into generated Prometheus scrape configuration. Specifically, unsafe fields such as bearerTokenFile and related tlsConfig file path options (including caFile, certFile, and keyFile) can be propagated into the OpenTelemetry Collector scrape configuration instead of being rejected or sanitized. If an attacker can create or modify a ServiceMonitor that is selected by the TargetAllocator configuration, they can point these settings at arbitrary files on the Collector pod filesystem. During scraping, the Collector will read those local files and use their contents in outbound requests to the configured scrape target, allowing exfiltration of sensitive local files. Exposed material can include the mounted Kubernetes service account token, certificates, private keys, and other tokens present in the pod.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.