Habr•July 24, 2026•🇷🇺Translated from Russian

Container Image Risks: Why Skipping Verification Today Breaks Your Service Tomorrow

Nikita, technical leader of the Evolution Container Security and Addons team at Cloud.ru, outlines four common container security pitfalls that repeatedly appear in client Kubernetes environments. The post covers vulnerable dependencies, supply-chain attacks on image registries, secret leakage in layers, and CI/CD exposure points, supported by concrete incidents from production clusters.

Thin spot 1. Untracked vulnerabilities in dependencies

The most frequent issue is outdated software carrying known CVE entries combined with overly permissive configurations. Small teams often stay current because their infrastructure is simple, while large enterprises remain on old versions due to extensive custom integrations but compensate with strict access policies. Mid-sized organizations face the worst position: custom wrappers already hinder updates, yet they lack dedicated security staff or tooling to offset the risk.

A 2025 vulnerability in nvidia-container-toolkit (CVE-2025-23266) illustrates the danger. The flaw resided in OCI hooks that execute with host privileges. An attacker could embed a malicious library inside a minimal Dockerfile; after escaping the container, the attacker enumerated pods, located a service account with nodes/proxy rights, and used the kubelet port 10250 to execute commands on another node, ultimately accessing mounted secrets. The incident combined the NVIDIA component vulnerability with excessive service-account privileges. A second high-severity flaw appeared in the same component shortly afterward, reinforcing that privileged add-ons such as GPU operators and CNI plugins require patching within days rather than weeks.

Thin spot 2. Supply chain attacks: even pinned tags are not safe

The classic advice to avoid the latest tag proved insufficient when attackers compromised Aqua Security developer accounts in early 2026. They performed force pushes that reassigned more than seventy Trivy tags to malicious commits containing secret-exfiltration logic. Later, using a remaining compromised service account, they published tainted images directly to Docker Hub. Organizations pulling fresh images without cache or additional verification could have deployed the malicious versions.

Cloud.ru avoided impact through a private registry with caching and mandatory manual review plus secondary scanning before promotion. The incident demonstrated that a tag can be silently rebound to different content; the only reliable reference is the full SHA256 digest of the image manifest. Additional protection comes from Cosign signatures verified inside the cluster by Connaisseur, Kyverno, or Image Validating Admission Policies. The article also notes the gh0stEdit class of attacks that can alter unpacked layer contents while preserving manifest hashes.

Thin spot 3. Secret leakage: regex-based detection still works

Developers continue to commit private keys and hardcoded credentials that end up baked into container layers. Two real cases involved a DevOps engineer who left an SSH key in a working directory before pushing, and a tester who hardcoded credentials that survived the build pipeline. Simply overwriting the file or rebuilding a new image does not remove the secret from Git history or from previously pushed image layers; rotation of the secret itself remains the only reliable remediation.

Effective controls begin with pre-commit hooks that block commits containing obvious secret patterns locally. Subsequent layers include CI/CD scanning with tools such as Trivy and Checkov, followed by registry-level scanning provided by Evolution Container Security.

Thin spot 4. CI/CD as an attack vector

The article concludes by noting that supply-chain and secret issues ultimately converge in CI/CD pipelines. Automated verification of image signatures, continuous vulnerability monitoring, and strict service-account hygiene are required to prevent a single compromised upstream image or leaked credential from granting cluster-wide access.

Related articles

BoletimSec•Supply Chain & Open Source

Uber Breach Exposes 149,000 Drivers After Third-Party Vendor Credentials Stolen

Uber has notified approximately 149,346 drivers that personal data was stolen in an October incident involving a compromised third-party vendor. Attackers used valid credentials belonging to the vendor to access data the ride-hailing company had shared with it, bypassing all security alerts because the access appeared legitimate. The affected information includes driver license images, names, addresses, dates of birth and government-issued identification numbers. The vendor was later identified as Fireworks AI, a cloud platform for running and fine-tuning open-source AI models. The same credential theft campaign had previously impacted Notion and Cursor. Uber immediately severed the connection upon discovery, notified regulators in multiple U.S. states, and is offering credit monitoring to affected individuals.

BoletimSec•Supply Chain & Open Source

FBI Warns of ARTEX AI Pentest Framework Abused by Cybercriminals with Backdoored Docker Images

The FBI has issued an alert regarding the open-source ARTEX AI-powered penetration testing framework after it was observed in criminal operations targeting banks, governments, and technology companies since August 2026. Attackers achieved privileged access in under three hours in multiple incidents. The Cloud Security Alliance identified compromised Docker images containing a backdoor that executes root commands without authentication by exploiting a hidden CAPTCHA field value passed to sh -c. Approximately 9,000 downloads occurred from one malicious image, and 62 exposed consoles were found running the tampered version. Check Point reported 1,608 internet-exposed ARTEX consoles, including ten with exposed databases. The original GitHub repository was removed in October 2026, yet third-party copies and images continue to circulate. CERT-EU highlighted the lack of technical restrictions preventing out-of-scope actions by autonomous AI agents.

AntiMalware•Supply Chain & Open Source

Optimizely Supply Chain Attack Infects BBC, CNN, HSBC and 177 Other Sites with Crypto-Stealing JavaScript

On November 16, visitors to major corporate websites received malicious JavaScript that swapped cryptocurrency wallet addresses and attempted to intercept banking card data. The code was distributed through Optimizely Web, a platform used for A/B testing. Researchers identified the malicious code in 188 scripts belonging to 178 organizations, including BBC, CNN, Fox News, HSBC, Equifax, Zoom, Salesforce, GitLab and IKEA. Attacker Scott Helm from Report URI reconstructed the attack timeline: adversaries modified the Project JavaScript field in client projects to load a file from an external domain while legitimate code continued to arrive from cdn.optimizely.com. The campaign began at 04:21 UTC on the BBC script and saw 26 payload updates throughout the day, including a card-data harvesting module added at 13:43 UTC. The malicious script could not access Stripe or Adyen payment forms inside iframes but attempted iOS exploit chains Coruna and DarkSword on affected devices. Optimizely confirmed the breach resulted from a vulnerability in Experimentation account registration, closed the flaw, removed the code and notified customers. Content Security Policy blocked the payload on only 24 of 256 tested sites, and attackers collected roughly $7,040 in cryptocurrency before cleanup completed around 21:52 UTC.

Habr•Supply Chain & Open Source

Rspamd 4.3.0 Released with Improved Phishing Detection, Attachment Scanning and Authentication Hardening

In mid-November 2026, developer Vsevolod Stakhov released Rspamd 4.3.0, the latest version of the open-source spam filtering system written in C, C++ and Lua under the Apache 2.0 license. The update strengthens HTTP connection handling, URL-based phishing checks, SPF/DKIM/ARC authentication validation and SMTPUTF8 address parsing while adding more robust attachment and HTML analysis. Key improvements include separate scoring for displayed versus actual link destinations, stricter rejection of weak DKIM keys and duplicate tags, and better archive filename handling to prevent executable hiding. The release also introduces the HTML_TINY_PIXEL_TRACKER rule to detect tracking beacons and fixes multiple bugs that could cause worker crashes or memory issues after free. Several changes may require configuration adjustments for existing users, particularly around symbol options and stricter authentication policies. Rspamd continues to support high-throughput Milter integration with Postfix and Sendmail while offering an extensive Lua API for custom processing logic.