# container images

Container images are standardized packages containing the files, binaries, libraries, and configurations needed to run a container; they are immutable and composed of layers.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## SonarQube container scanning is now generally available

DevFeed: [SonarQube container scanning is now generally available](<https://devfeed.tech/articles/sonarqube-container-scanning-is-now-generally-available-146295.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/sonarqube-container-scanning-is-now-available/>)

Author: Satinder Khasriya

Published: 2026-11-19T14:00:00Z

Content type: release

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container image vulnerabilities](<https://devfeed.tech/topics/container-image-vulnerabilities.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fail](<https://devfeed.tech/tags/fail.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [organization](<https://devfeed.tech/tags/organization.md>), [results](<https://devfeed.tech/tags/results.md>), [risks](<https://devfeed.tech/tags/risks.md>), [scan](<https://devfeed.tech/tags/scan.md>), [scanner](<https://devfeed.tech/tags/scanner.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [security](<https://devfeed.tech/tags/security.md>), [sonarqube](<https://devfeed.tech/tags/sonarqube.md>), [sonarqube-advanced-security](<https://devfeed.tech/tags/sonarqube-advanced-security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Container scanning is generally available in SonarQube Advanced Security on SonarQube Cloud for Team and Enterprise plan customers, at no additional cost. It scans built and shipped container images for known vulnerabilities and malicious packages. Results appear under Container images in the organization and use the same workflow as dependency risks. CI builds can be configured to fail when findings meet or exceed a chosen severity. The supplied excerpt does not describe setup steps or scanner limitations.

### Source excerpt

Scan the container images you ship for known vulnerabilities and malicious packages. Now generally available in SonarQube Advanced Security. Learn more

## Java4Shell: What Keycloak admins need to do (CVE-2026-114938)

DevFeed: [Java4Shell: What Keycloak admins need to do (CVE-2026-114938)](<https://devfeed.tech/articles/java4shell-what-keycloak-admins-need-to-do-cve-2026-114938-141089.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938>)

Author: The Keycloak team

Published: 2026-11-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [Keycloak Blog](<https://devfeed.tech/sources/keycloak-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [avx](<https://devfeed.tech/tags/avx.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [base64](<https://devfeed.tech/tags/base64.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [container](<https://devfeed.tech/tags/container.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [idm](<https://devfeed.tech/tags/idm.md>), [java](<https://devfeed.tech/tags/java.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [machine](<https://devfeed.tech/tags/machine.md>), [memory](<https://devfeed.tech/tags/memory.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

CVE-2026-114938 ("Java4Shell") affects Keycloak when it uses an unpatched OpenJDK build from 17.0.6 onward, the x86-64 host exposes AVX-512 VBMI, and the live JVM has Base64 intrinsics enabled. The flaw can corrupt memory through pre-authentication requests; researchers report demonstrating remote code execution. Check the Java runtime, CPU feature, and effective flags on every Keycloak node, including failover and rollout nodes. Red Hat's preferred interim mitigation is `-XX:-UseBASE64Intrinsics`, followed by restarting and verifying each JVM with `jcmd`; limiting AVX to AVX2 is another relevant condition, but the post favors disabling the intrinsic. The Operator is a separate JVM and needs its own mitigation; configuring it does not configure managed Keycloak pods. The cited 26.8.2-1 and 26.8.2-2 x86-64 images bundle affected OpenJDK 21.0.13, but image tags alone do not establish exploitability. Use a vendor-confirmed fixed runtime when available; the post says no specific fixed Keycloak image could yet be recommended.

### Source excerpt

Last updated: 18 November 2026, 09:29 UTC If your organization uses Keycloak, please pass this post to the team that operates it, even if you do not run Keycloak yourself. They need to check the Java runtime and the CPU type used by every Keycloak instance. The issue is CVE-2026-114938, known as Java4Shell. The flaw is in OpenJDK's accelerated Base64 decoder, which Keycloak uses to process some requests. On affected systems, a malformed value that Keycloak decodes before authentication can corrupt the Java process's memory. The researchers report that they demonstrated pre-authentication remote code execution against Keycloak. Am I affected? Treat a Keycloak instance as at risk when all of these apply: It runs an unpatched OpenJDK build from 17.0.6 onward, including unpatched OpenJDK 21 and 25 builds. Its x86-64 host or virtual machine exposes the avx512vbmi CPU feature to Java. The running JVM has Base64 intrinsics enabled and has not been limited to AVX2 with -XX:UseAVX=2. As checked on 18 November 2026, the x86-64 Keycloak container images tagged 26.8.2-1 and 26.8.2-2 bundle an affected OpenJDK 21.0.13 build. These image tags alone do not establish whether your deployment is exploitable: check the CPU feature and effective JVM flags as described below. A Keycloak ZIP or TAR.GZ distribution started directly on a host can also be affected; the conditions depend on its Java runtime and CPU, not on whether it runs in a container. Keycloak processes Base64 data on requests that arrive before authentication, so administrators should not assume that a login requirement protects an affected instance. Check every node or virtual machine that can run Keycloak, including failover nodes and nodes used during rolling updates. A check on your workstation does not establish the status of a production deployment. On the Keycloak host or virtual machine, check the CPU feature: grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available' If this prints no

## Cloud keys leaked in Docker Hub images are stolen within seconds

DevFeed: [Cloud keys leaked in Docker Hub images are stolen within seconds](<https://devfeed.tech/articles/cloud-keys-leaked-in-docker-hub-images-are-stolen-within-seconds-138535.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/cloud-keys-leaked-in-docker-hub-images-are-stolen-within-seconds/>)

Author: Bill Toulas

Published: 2026-11-17T21:27:17Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [token jacking](<https://devfeed.tech/topics/token-jacking.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-api](<https://devfeed.tech/tags/anthropic-api.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [business-email-compromise](<https://devfeed.tech/tags/business-email-compromise.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [honeypot](<https://devfeed.tech/tags/honeypot.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [key](<https://devfeed.tech/tags/key.md>), [keys](<https://devfeed.tech/tags/keys.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [public](<https://devfeed.tech/tags/public.md>), [published](<https://devfeed.tech/tags/published.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

In a four-month experiment, researchers published 300 honeypot images across eight public container registries and found exposed credentials could be exploited within seconds. On Docker Hub, the fastest planted AWS key use came 7.86 seconds after publication; the median first call was 51.19 seconds, and all 100 AWS keys were used within 15 minutes. The keys received more than 140,000 API calls from 5,000 unique IP addresses, while exposed OpenAI and Anthropic keys were used to exhaust test-account balances. Monitoring rarely detected containers being run, suggesting scanners usually extracted secrets by inspecting image layers or querying registry APIs. The researchers recommend scanning images for secrets before publication and restricting or rate-limiting access to Docker Hub's feed of recently updated images. In an August check, they found no changes to platform defenses.

### Source excerpt

Credentials and access secrets exposed in public Docker Hub images are being extracted and exploited by attackers within as little as eight seconds of publication. [...]

## AlmaLinux OS 10.3 and 9.9 are now available

DevFeed: [AlmaLinux OS 10.3 and 9.9 are now available](<https://devfeed.tech/articles/almalinux-os-10-3-and-9-9-are-now-available-135945.md>)

Original publisher: [Read original article](<https://almalinux.org/blog/2026-11-16-almalinux_103_and_99_stable/>)

Author: Andrew Lukoshko AlmaLinux Lead Architect; ALESCo Member

Published: 2026-11-16T00:00:00Z

Content type: release

Language: en

Sources: [AlmaLinux](<https://devfeed.tech/sources/blog-on-almalinux.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [almalinux](<https://devfeed.tech/tags/almalinux.md>), [audit](<https://devfeed.tech/tags/audit.md>), [beta](<https://devfeed.tech/tags/beta.md>), [community](<https://devfeed.tech/tags/community.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [gcc](<https://devfeed.tech/tags/gcc.md>), [gdb](<https://devfeed.tech/tags/gdb.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [go](<https://devfeed.tech/tags/go.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [llvm](<https://devfeed.tech/tags/llvm.md>), [logging](<https://devfeed.tech/tags/logging.md>), [ml-kem](<https://devfeed.tech/tags/ml-kem.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [node-js-26](<https://devfeed.tech/tags/node-js-26.md>), [os](<https://devfeed.tech/tags/os.md>), [rust](<https://devfeed.tech/tags/rust.md>), [security](<https://devfeed.tech/tags/security.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

AlmaLinux OS 10.3 and 9.9 are generally available, with updated development tools and security packages. AlmaLinux 10.3 restores ModSecurity with CRS 4.22, so administrators carrying rules forward from AlmaLinux 9 should review them before production use. Its Podman 6 update removes CNI, BoltDB, slirp4netns, cgroups v1, and iptables support; Netavark, SQLite, pasta, and nftables are used instead. Across both releases, authselect no longer merges groups by default, fapolicyd advances to 2.0, and GCC Toolset 16 defaults to C++20. The announcement recommends testing existing fapolicyd rules and trust databases on a non-production host. AlmaLinux also reports adding kernel fixes absent from the corresponding RHEL releases: 44 CVE fixes for 9.9 and 36 for 10.3.

### Source excerpt

Hello Community! The AlmaLinux OS Foundation is announcing the general availability of AlmaLinux OS 10.3 codenamed "Mauve Lion" and AlmaLinux OS 9.9 codenamed "Chartreuse Bobcat"! Thank you to everyone who tested the 10.3 beta and 9.9 beta. AlmaLinux OS 10.3 "Mauve Lion" AlmaLinux 10.3 (kernel 6.12.0-264.16.1.el10_3) adds GCC Toolset 16, LLVM Toolset 22, Rust 1.97, Go 1.27, GDB 17.2, and Node.js 26. Security updates include fapolicyd 2.0, Keylime 7.14, audit 4.2 with post-quantum TLS for remote logging, and libreswan 5.4 with ML-KEM post-quantum key exchange.

## Run GitLab-certified hardened images for GitLab Enterprise Edition with the security of Chainguard

DevFeed: [Run GitLab-certified hardened images for GitLab Enterprise Edition with the security of Chainguard](<https://devfeed.tech/articles/run-gitlab-certified-hardened-images-for-gitlab-enterprise-edition-with-the-security-of-chainguard-133959.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/run-gitlab-certified-hardened-images-for-gitlab-enterprise-edition-with-the-security-of-chainguard>)

Published: 2026-11-13T00:00:00Z

Content type: release

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard commercial builds](<https://devfeed.tech/topics/chainguard-commercial-builds.md>), [chainguard images](<https://devfeed.tech/topics/chainguard-images.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [chainguard sboms](<https://devfeed.tech/topics/chainguard-sboms.md>), [chainguard cve remediation](<https://devfeed.tech/topics/chainguard-cve-remediation.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [fips 140-3](<https://devfeed.tech/topics/fips-140-3.md>), [containers for fedramp](<https://devfeed.tech/topics/containers-for-fedramp.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [audit](<https://devfeed.tech/tags/audit.md>), [bloat](<https://devfeed.tech/tags/bloat.md>), [build](<https://devfeed.tech/tags/build.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [cves](<https://devfeed.tech/tags/cves.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fips](<https://devfeed.tech/tags/fips.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hardened-images](<https://devfeed.tech/tags/hardened-images.md>), [images](<https://devfeed.tech/tags/images.md>), [sboms](<https://devfeed.tech/tags/sboms.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Organizations can keep their existing GitLab Enterprise Edition license while Chainguard maintains GitLab-certified hardened container images. GitLab runs its end-to-end QA suite against each release; images include SBOM, provenance, and signature artifacts and are built through Chainguard Factory, described as SLSA Level 3-compliant. The images omit shells, package managers, and other unnecessary components, and Chainguard states remediation timelines of 7 days for critical CVEs and 14 days for other severities. FIPS-ready variants are available. An active GitLab subscription is required: Chainguard handles image rebuilds, CVE remediation, and image-related support under its support plan, while GitLab provides application support through its subscription. Chainguard coordinates with GitLab on vulnerability remediation and daily rebuilds.

### Source excerpt

Secure GitLab Enterprise Edition with Chainguard's certified hardened container images, featuring minimal CVEs, signed SBOMs, and FIPS-ready options.

## Critical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a Registry

DevFeed: [Critical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a Registry](<https://devfeed.tech/articles/critical-red-hat-quay-flaw-lets-attackers-read-and-overwrite-all-private-container-images-in-a-registry-130611.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/critical-red-hat-quay-flaw-lets.html>)

Author: The Hacker News

Published: 2026-11-12T16:27:01Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [container images](<https://devfeed.tech/topics/container-images.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-110697](<https://devfeed.tech/tags/cve-2026-110697.md>), [cve-2026-123710](<https://devfeed.tech/tags/cve-2026-123710.md>), [quay](<https://devfeed.tech/tags/quay.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [registry](<https://devfeed.tech/tags/registry.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The supplied text describes two critical Red Hat Quay flaws. CVE-2026-123710 lets an attacker add a non-expiring signing key that Quay trusts for any repository, enabling private image access, image pushes or overwrites, and deletion of keys used by running instances. Anonymous access is not required if the attacker has a valid account. Red Hat recommends restricting access to /keys, checking audit logs for unexpected key events, removing unknown keys, and installing a fixed release; removing a key alone is temporary until patched. CVE-2026-110697 lets a user who can create a namespace exploit unescaped underscores in SQL LIKE matching to retrieve other tenants' robot tokens and access their images. Red Hat says updating is the only complete fix; interim steps include restricting creation of underscore namespaces, rotating potentially exposed robot tokens, and monitoring unusual pulls or pushes. The text also notes mismatches between the cited CVE entry and advisories on affected or fixed status.

### Source excerpt

Critical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a Registry A critical flaw in Red Hat Quay allows an attacker who can access a Quay registry to read and overwrite private container images in every repository. Quay enables anonymous access by default, and whil ... Read more Published Date: Nov 12, 2026 (1 hour, 15 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-110697 CVE-2026-123710

## Critical Red Hat Quay Vulnerability Could Expose Private Container Images

DevFeed: [Critical Red Hat Quay Vulnerability Could Expose Private Container Images](<https://devfeed.tech/articles/critical-red-hat-quay-vulnerability-could-expose-private-container-images-130132.md>)

Original publisher: [Read original article](<https://www.securityweek.com/critical-red-hat-quay-vulnerability-could-expose-private-container-images/>)

Author: Eduard Kovacs

Published: 2026-11-12T09:23:21Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [Exploit](<https://devfeed.tech/topics/exploit.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [content](<https://devfeed.tech/tags/content.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-vulnerability](<https://devfeed.tech/tags/critical-vulnerability.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123710](<https://devfeed.tech/tags/cve-2026-123710.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-score](<https://devfeed.tech/tags/cvss-score.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [quay](<https://devfeed.tech/tags/quay.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CVE-2026-123710 is a critical Red Hat Quay flaw (CVSS 9.8) affecting deployments where the signing-key management service is accessible to untrusted clients. Anonymous attackers can exploit key rotation to install a trusted signing key and mint tokens with read and write access to any repository. This could expose private images and embedded secrets, enable image replacement, and disrupt registry operations. The malicious key can persist across restarts; disabling anonymous access, changing passwords, or regenerating robot tokens does not remove it, and valid Quay accounts can also exploit the flaw. Red Hat recommends restricting access to the service, checking logs for suspicious key changes, and removing unauthorized keys, but warns attackers may reinstall them until a fix is deployed. Fixes were merged into GitHub on November 11; the excerpt does not identify a fixed release.

### Source excerpt

Attackers could exploit a critical Red Hat Quay flaw to steal private container images, overwrite repositories and maintain persistent access. The post Critical Red Hat Quay Vulnerability Could Expose Private Container Images appeared first on SecurityWeek.

## Build container images on your Runpod Pod with Runpod Weld

DevFeed: [Build container images on your Runpod Pod with Runpod Weld](<https://devfeed.tech/articles/build-container-images-on-your-runpod-pod-with-runpod-weld-124884.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/runpod-weld-build-images-on-your-pod>)

Author: Roman Przybyla

Published: 2026-11-09T23:41:48Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [Docker Image](<https://devfeed.tech/topics/docker-image.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [demo](<https://devfeed.tech/tags/demo.md>), [docker](<https://devfeed.tech/tags/docker.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [inside](<https://devfeed.tech/tags/inside.md>), [pod](<https://devfeed.tech/tags/pod.md>)

### AI overview

Runpod Weld builds and pushes container images from a Runpod Pod without a Docker daemon; a separate container runtime is needed to run them. The guide shows checking the Pod with `rpweld doctor`, installing Weld on Linux amd64 (Debian 12 is the validated target), preparing a Dockerfile, and building and pushing an image to Docker Hub. Weld caches build stages, but builds are slower than local Docker, support only a subset of Dockerfile syntax, and are alpha software. Builds need Pod capabilities and filesystem permissions for `RUN` steps; Weld is not a security sandbox, and trusted Dockerfiles are recommended because `RUN` commands can access the Pod. Its image store and cache are separate from Docker's, finished builds are not automatically deleted, and registry tokens are base64-encoded rather than encrypted. The guide demonstrates deploying the pushed image on Runpod or running it on a Linux amd64 Docker host, and notes that private images require registry credentials.

### Source excerpt

Runpod Weld builds and pushes container images from inside a Runpod Pod, no Docker daemon needed. Build a demo image, push it, and run it on a Pod.

## Vercel Container Registry now supports 2 GB compressed image layers

DevFeed: [Vercel Container Registry now supports 2 GB compressed image layers](<https://devfeed.tech/articles/vercel-container-registry-now-supports-2-gb-compressed-image-layers-124307.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-container-registry-now-supports-2-gb-compressed-image-layers>)

Author: Andy Waller

Published: 2026-11-09T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [container images](<https://devfeed.tech/topics/container-images.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [docker](<https://devfeed.tech/tags/docker.md>), [error](<https://devfeed.tech/tags/error.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [image](<https://devfeed.tech/tags/image.md>), [layers](<https://devfeed.tech/tags/layers.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [public](<https://devfeed.tech/tags/public.md>), [retries](<https://devfeed.tech/tags/retries.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Container Registry now supports compressed image layers up to 2 GB each, increased from 500 MB, while the total image size limit remains 15 GB. It supports standard Docker push, pull, and tag workflows; pushing an image creates its repository automatically. Repositories can allow read-only pulls by any Vercel team or be shared with up to 100 selected teams. Vercel CLI v58.3.0 or later provides `vercel vcr` management commands, and GitHub Actions can authenticate through `vercel/vcr-action/login` with GitHub OIDC, avoiding long-lived registry credentials. If background image optimization fails, the dashboard reports an error; pushing the same image again retries conversion.

### Source excerpt

Vercel Container Registry now supports compressed image layers of up to 2 GB each, up from 500 MB, the total image size limit stays 15 GB. The registry works with standard workflows like docker push, docker pull, and docker tag, and pushing an image creates the repository on the fly. Repositories can be made public for read-only pull access by any Vercel team, or shared with specific teams up to 100 from the dashboard or with vercel vcr permissions. The Vercel Managed Images that Vercel Sandbox runs on are served from ordinary public repositories, built with the same public-repository feature any team can use for its own images. Manage repositories, images, and tags with the vercel vcr CLI commands in Vercel CLI v58.3.0 or later, and log CI workflows in from GitHub Actions with the vercel/vcr-action/login action using GitHub OIDC, which removes the need for long-lived registry credentials. If background optimization of a pushed image fails, the image shows an error status in the dashboard, and pushing the same image again retries the conversion. See the documentation for the full setup. Read more

## Virtualization security: attack layers and misconfiguration impact

DevFeed: [Virtualization security: attack layers and misconfiguration impact](<https://devfeed.tech/articles/virtualization-security-attack-layers-and-misconfiguration-impact-121827.md>)

Original publisher: [Read original article](<https://securelist.com/virtualization-security-esxi-and-proxmox-ransomware-cases/121819/>)

Author: Rauf Johari

Published: 2026-11-06T10:00:12Z

Content type: article

Language: en

Sources: [Securelist](<https://devfeed.tech/sources/securelist.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [ransomware](<https://devfeed.tech/topics/ransomware.md>), [Proxmox](<https://devfeed.tech/topics/proxmox.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [container](<https://devfeed.tech/topics/container.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [container image vulnerabilities](<https://devfeed.tech/topics/container-image-vulnerabilities.md>)

Tags: [attack](<https://devfeed.tech/tags/attack.md>), [cases](<https://devfeed.tech/tags/cases.md>), [containers](<https://devfeed.tech/tags/containers.md>), [credentials-theft](<https://devfeed.tech/tags/credentials-theft.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [esxi](<https://devfeed.tech/tags/esxi.md>), [full](<https://devfeed.tech/tags/full.md>), [impact](<https://devfeed.tech/tags/impact.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [large](<https://devfeed.tech/tags/large.md>), [layers](<https://devfeed.tech/tags/layers.md>), [medium](<https://devfeed.tech/tags/medium.md>), [passwords](<https://devfeed.tech/tags/passwords.md>), [proxmox](<https://devfeed.tech/tags/proxmox.md>), [ransomware](<https://devfeed.tech/tags/ransomware.md>), [security](<https://devfeed.tech/tags/security.md>), [soc-ti-and-ir-posts](<https://devfeed.tech/tags/soc-ti-and-ir-posts.md>), [thumbnail](<https://devfeed.tech/tags/thumbnail.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>), [virtualization-security](<https://devfeed.tech/tags/virtualization-security.md>), [vmware](<https://devfeed.tech/tags/vmware.md>)

### AI overview

Two ransomware investigations show how ordinary administrative access can spread into a virtual environment: one attacker reused an ESXi root password available through an overprivileged PRTG monitoring setup and connected by SSH; another found Proxmox root credentials in plain-text notes on a compromised administrator workstation and used the VNC web socket. Neither case required a VM escape. The text recommends separating monitoring from administration, limiting identities and network paths, using unique vaulted credentials, routing routine ESXi management through vCenter, keeping SSH off except for restricted support windows, and alerting on security configuration changes. It also highlights platform-specific risks: VMs use a separate guest kernel, while containers share the host kernel and can lose isolation through kernel/runtime flaws or unsafe settings such as privileged mode and writable host mounts. Image provenance, management APIs, virtual network segmentation, protected logs, and isolated backups are additional control areas.

### Source excerpt

A detailed breakdown of misconfigurations in virtual environment cybersecurity as shown by examples of ransomware cases on ESXi and Proxmox environments.

## Docker and ActiveState Extending Secure Defaults to the Packages Developers Install

DevFeed: [Docker and ActiveState Extending Secure Defaults to the Packages Developers Install](<https://devfeed.tech/articles/docker-and-activestate-extending-secure-defaults-to-the-packages-developers-install-119503.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-activestate-trusted-content/>)

Author: Vishrut Iyengar

Published: 2026-11-05T15:28:22Z

Content type: release

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [npm](<https://devfeed.tech/topics/npm.md>), [pip](<https://devfeed.tech/topics/pip.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [axios](<https://devfeed.tech/tags/axios.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [built-from-source](<https://devfeed.tech/tags/built-from-source.md>), [content](<https://devfeed.tech/tags/content.md>), [developers](<https://devfeed.tech/tags/developers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hardened-images](<https://devfeed.tech/tags/docker-hardened-images.md>), [packages](<https://devfeed.tech/tags/packages.md>), [partners](<https://devfeed.tech/tags/partners.md>), [partnerships](<https://devfeed.tech/tags/partnerships.md>), [products](<https://devfeed.tech/tags/products.md>), [secure-defaults](<https://devfeed.tech/tags/secure-defaults.md>), [security](<https://devfeed.tech/tags/security.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [standard](<https://devfeed.tech/tags/standard.md>), [teams](<https://devfeed.tech/tags/teams.md>), [trusted-supply-chain](<https://devfeed.tech/tags/trusted-supply-chain.md>)

### AI overview

Docker and ActiveState extend supply chain controls from container images to application dependencies. Docker Hardened Images (DHI) are minimal, source-built images with signed SBOMs, SLSA Level 3 provenance, full CVE visibility, and--on paid tiers--a 7-day SLA for critical and high CVEs. ActiveState's Curated Catalog is a policy-governed repository containing team-approved packages, compiled from source with SLSA Level 3 provenance and complete SBOMs; it automatically rebuilds components after upstream fixes, with SLAs of 5 business days for critical CVEs and 10 for high CVEs. Teams can route Artifactory or Nexus through the catalog while developers and coding assistants retain familiar pip and npm workflows. The article says these controls complement pinned digests, cooldown periods, and sandboxed agents; the integration does not replace them.

### Source excerpt

Docker partners with ActiveState to continue to provide one standard for trusted content across everything you and your teams build on.

## Post Mortem: Patching the PHP and Node.js Vulnerabilities

DevFeed: [Post Mortem: Patching the PHP and Node.js Vulnerabilities](<https://devfeed.tech/articles/post-mortem-patching-the-php-and-node-js-vulnerabilities-117685.md>)

Original publisher: [Read original article](<https://laravel.com/blog/php-nodejs-vulnerabilities-post-mortem>)

Author: Aaron Francis

Published: 2026-11-04T19:15:00Z

Content type: article

Language: en

Sources: [Laravel Blog](<https://devfeed.tech/sources/laravel-blog.md>)

Topics: [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [PHP](<https://devfeed.tech/topics/php.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [disclosures](<https://devfeed.tech/tags/disclosures.md>), [forge](<https://devfeed.tech/tags/forge.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php](<https://devfeed.tech/tags/php.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Laravel Cloud patched every running application in place within about five hours of the PHP release, with no customer action or downtime reported. Its Kubernetes operator installed patched PHP binaries and restarted workloads in paced waves; the team accelerated the restart pacing fivefold, used canaries, and temporarily paused new Cloud deployments. A Cloudflare managed firewall ruleset added protection while the patch was prepared, but the article says it could not replace patching. Building its own PHP image let Laravel ship before Docker Hub's patched images were available. Other products required different responses: Forge customers had to upgrade PHP, and a surge of jobs starved deployments, leading to about 4,800 cancellations; Envoyer went offline for server upgrades; Vapor customers needed to redeploy for new runtimes and images. The team says it is adding recovery soak periods and recorded war rooms, separating Forge's deployment queue, modernizing Envoyer, and reviewing Vapor's redeployment policy.

### Source excerpt

How we patched every Laravel Cloud app in place within about 27 hours of the PHP and Node.js disclosures, what broke on Forge, Envoyer, and Vapor, and what we are changing.

## OpenShell on Kubernetes: A guide for platform engineers

DevFeed: [OpenShell on Kubernetes: A guide for platform engineers](<https://devfeed.tech/articles/openshell-on-kubernetes-a-guide-for-platform-engineers-117173.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/11/04/openshell-on-kubernetes-a-guide-for-platform-engineers/>)

Author: Jim Bugwadia, Nirmata

Published: 2026-11-04T12:00:00Z

Content type: article

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [OpenShell](<https://devfeed.tech/topics/openshell.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Helm charts](<https://devfeed.tech/topics/helm-charts.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [openshell](<https://devfeed.tech/tags/openshell.md>), [platform](<https://devfeed.tech/tags/platform.md>)

### AI overview

OpenShell runs each agent in a sandbox and routes its outbound requests through a supervisor that can enforce per-binary, per-host, port, and HTTP-method rules, mediate credentials, and accept policy updates without restarting. On Kubernetes it uses SIG Apps' Agent Sandbox, so sandboxes appear as familiar Kubernetes resources; creation currently goes through the Gateway API, and a Supervisor Pod per agent may limit scale. The runtime checks key Pod security settings, while platform teams remain responsible for image, resource, credential, and access controls. The guide pairs RBAC with Kyverno admission policies for those settings and notes that the demo's gateway service account can still create Pods and NetworkPolicies directly, which production policies should cover. Compared with OpenShell's per-request controls and Kubernetes-visible objects, Agent Substrate uses a shared egress gateway, its own API and scheduler, and gVisor or Cloud Hypervisor isolation; it separates agent count from worker-pool Pod count, which may suit many bursty, idle agents. A proposed Substrate isolation backend for OpenShell remains incomplete in the excerpt.

### Source excerpt

What OpenShell is AI agents do more than call APIs. They run shells, install packages, read files, and open network connections. Often they act on text they pulled from the internet a minute earlier. So every...

## Secure your containers without breaking what works

DevFeed: [Secure your containers without breaking what works](<https://devfeed.tech/articles/secure-your-containers-without-breaking-what-works-116036.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/04/rapidfort-runtime-container-profiling/>)

Author: Help Net Security

Published: 2026-11-04T06:00:34Z

Content type: tutorial

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [container-security](<https://devfeed.tech/topics/container-security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [distroless](<https://devfeed.tech/topics/distroless.md>)

Tags: [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automation](<https://devfeed.tech/tags/automation.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [expert-analysis](<https://devfeed.tech/tags/expert-analysis.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [news](<https://devfeed.tech/tags/news.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [packages](<https://devfeed.tech/tags/packages.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Container hardening can reduce attack surface safely by using observed runtime behavior to guide removals, then validating each rebuilt image. An SBOM inventories installed components; an RBOM records components observed in use, helping distinguish what is present from what profiling exercised. Profile under representative conditions--including functional tests, staging or production traffic where appropriate, load and stress tests, and fuzzing--then remove unobserved components at an intensity suited to the service, with keep lists for justified exceptions. Treat functional and integration tests as a release gate, retain the original image for rollback, and feed validation findings into the next baseline. CI/CD systems such as GitHub Actions, GitLab CI, or Jenkins can automate profiling, rebuilding, validation, and drift alerts, while teams remain accountable for removal choices, exceptions, and approvals. Because untested paths may need components, repeat profiling and validation as images change; observed use is evidence, not proof of complete coverage.

### Source excerpt

Container security has a familiar problem. Teams identify vulnerabilities, but turning those findings into lower risk is much harder. A standard container image may include operating-system packages, development tools, debugging utilities and libraries that an application never uses. Each unnecessary component can expand the attack surface and add vulnerabilities to investigate, patch or explain during an audit. Consider an NGINX image that contains 274 categorized vulnerabilities straight from download. Scanning makes those findings visible, but ... More -> The post Secure your containers without breaking what works appeared first on Help Net Security.

## How to run I/O workloads on OpenShift Virtualization VMs

DevFeed: [How to run I/O workloads on OpenShift Virtualization VMs](<https://devfeed.tech/articles/how-to-run-i-o-workloads-on-openshift-virtualization-vms-115666.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/03/how-run-io-workloads-openshift-virtualization-vms>)

Author: Elvir Kuric

Published: 2026-11-03T14:00:00Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [virtualization](<https://devfeed.tech/topics/virtualization.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [systems](<https://devfeed.tech/topics/systems.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [ci](<https://devfeed.tech/tags/ci.md>), [containerized](<https://devfeed.tech/tags/containerized.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [linux](<https://devfeed.tech/tags/linux.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [performance-and-scale-engineering](<https://devfeed.tech/tags/performance-and-scale-engineering.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

The `fio-container` harness makes Linux FIO testing repeatable across OpenShift Virtualization VMs: configure a workload matrix once, run it in parallel through `virtctl`, and collect per-VM JSON results in a shared directory for cross-run analysis. You can target pre-created VMs or set `CREATE_VMS=true` to provision Linux guests in the same job. YAML suits complex runs; environment variables support quick or CI runs. Storage modes cover a formatted and mounted data disk, raw block-device I/O, or a writable test directory on the OS disk. The harness prepares storage, installs FIO when needed, pre-writes data, runs the workload combinations, and gathers results. A bastion needs cluster access, Podman, and passwordless guest SSH; provisioning also requires a namespace and storage class. The article's detailed examples cover Linux. It also describes SSH-only use with bare-metal, KVM, and VMware Linux hosts; Windows guidance is deferred to `README-container.md`.

### Source excerpt

Editor's note This post was originally published in October 2025 and has been updated to reflect the latest containerized FIO test harness and automated VM provisioning workflows. The post How to run I/O workloads on OpenShift Virtualization VMs appeared first on Red Hat Developer.

## ColdFusion Kubernetes Ephemeral Storage Filling From Application Logs

DevFeed: [ColdFusion Kubernetes Ephemeral Storage Filling From Application Logs](<https://devfeed.tech/articles/coldfusion-kubernetes-ephemeral-storage-filling-from-application-logs-109723.md>)

Original publisher: [Read original article](<https://blog.devops.dev/coldfusion-kubernetes-ephemeral-storage-filling-from-application-logs-d2343c499c2e?source=rss----33f8b2d9a328---4>)

Author: Deepak Purohit

Published: 2026-10-30T18:59:31Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Cloud Logging](<https://devfeed.tech/topics/cloud-logging.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [adobe](<https://devfeed.tech/tags/adobe.md>), [adobe-coldfusion](<https://devfeed.tech/tags/adobe-coldfusion.md>), [alert](<https://devfeed.tech/tags/alert.md>), [coldfusion](<https://devfeed.tech/tags/coldfusion.md>), [coldfusion-development](<https://devfeed.tech/tags/coldfusion-development.md>), [container](<https://devfeed.tech/tags/container.md>), [ephemeral-storage](<https://devfeed.tech/tags/ephemeral-storage.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [pod](<https://devfeed.tech/tags/pod.md>), [storage](<https://devfeed.tech/tags/storage.md>), [volumes](<https://devfeed.tech/tags/volumes.md>)

### AI overview

ColdFusion logs can silently fill a pod's ephemeral storage and trigger pod or node evictions. Kubernetes counts writable layers, pod logs, and local emptyDir volumes; enforcement depends on local storage measurement being enabled. The excerpt recommends bounding ColdFusion output with maxOutLogSize and maxFileBackup in neo-logging.xml, checking cflog files for applicable rotation limits, and baking configuration into the image. Routing logs to stdout lets kubelet rotation apply (documented defaults: 10 MiB and five files), while writing to a file and streaming the same lines to stdout can double storage use. Set ephemeral-storage requests and limits, use size-limited emptyDir for scratch files, and ship logs off-node with a DaemonSet agent. Check filesystem layout and ColdFusion image behavior, since these vary; storage limits may not be enforced if measurement is unavailable, and QoS does not protect pods from disk-pressure evictions.

### Source excerpt

ColdFusion Kubernetes Ephemeral Storage Filling From Application LogsThe Disk You Forgot You Had: Stopping ColdFusion Logs From Filling Kubernetes Ephemeral Storage Your pods were stable for six weeks. Then, within an hour, three of them were evicted. Nothing changed in the code. Traffic was ordinary. Memory and CPU graphs looked healthy. The cause was a log file. One ColdFusion instance had been writing steadily to disk since the last deployment, and that disk was never meant to hold anything for long. When it filled, Kubernetes evicted the pod to protect the node. This failure mode is easy to miss because log volume grows slowly and silently. There is no spike to alert on. The pod simply reaches a ceiling nobody configured, often weeks after release. This guide explains what ephemeral storage actually includes, why ColdFusion fills it, and how to cap it. It uses the Kubernetes documentation and Adobe's own logging guidance. Lucid Outsourcing Solutions helps enterprise teams run ColdFusion containers that stay healthy for months, not weeks. What Counts as Ephemeral Storage? More than most teams expect. The Kubernetes ephemeral storage documentation states the purpose directly: "Pods use ephemeral local storage for scratch space, caching, and for logs." Logs are named explicitly. They are not an edge case; they are one of the three intended uses, and they are the one that grows without bound. The documentation also notes that the kubelet uses this same storage for container images and the writable layers of running containers. So your application competes with the platform for the same space. The resource management documentation lists what Kubernetes tracks toward usage. It counts writes to the container's writable layer, container images, or both. It counts local emptyDir volumes. It counts the Pod's own logs, usually under /var/log/pods. And it counts system files mapped into the Pod, such as /etc/hosts. Measurement is conditional, which matters later. The docume

## Blog: Falco 0.45.2: security updates and a look back at 0.45.1

DevFeed: [Blog: Falco 0.45.2: security updates and a look back at 0.45.1](<https://devfeed.tech/articles/blog-falco-0-45-2-security-updates-and-a-look-back-at-0-45-1-110695.md>)

Original publisher: [Read original article](<https://falco.org/blog/falco-0-45-2/>)

Published: 2026-10-30T00:00:00Z

Content type: release

Language: en

Sources: [Falco](<https://devfeed.tech/sources/falco-falco.md>)

Topics: [Falco](<https://devfeed.tech/topics/falco.md>), [Security](<https://devfeed.tech/topics/security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [blog](<https://devfeed.tech/tags/blog.md>), [buster](<https://devfeed.tech/tags/buster.md>), [ca](<https://devfeed.tech/tags/ca.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [clients](<https://devfeed.tech/tags/clients.md>), [community](<https://devfeed.tech/tags/community.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container](<https://devfeed.tech/tags/container.md>), [crash](<https://devfeed.tech/tags/crash.md>), [custom](<https://devfeed.tech/tags/custom.md>), [debian](<https://devfeed.tech/tags/debian.md>), [falco](<https://devfeed.tech/tags/falco.md>), [release](<https://devfeed.tech/tags/release.md>), [security](<https://devfeed.tech/tags/security.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Falco 0.45.2 updates CA trust stores in its Wolfi and Debian images and driver-loader images to address the eMudhra intermediate CA compromise; DEB/RPM users and deployments with custom CA bundles must update those separately. It also includes Falcoctl 0.14.3, container plugin 0.7.6, and OpenSSL 3.5.9 LTS. OpenSSL's default TLS security level is now 2, requiring RSA, DSA, and DH keys of at least 2048 bits and elliptic-curve keys of at least 224 bits; weaker legacy HTTPS endpoints may fail to connect. The release includes 0.45.1 reliability fixes for a Prometheus scrape race, file output recovery with keep_alive (the failed alert is not replayed), reloads when watched files disappear, and package installation on hosts without modern eBPF support. Separately deployed Falcosidekick needs its own update to 2.35.1 for trust and Go security updates. Helm chart 9.2.2 defaults to Falco 0.45.2 and related component versions; review explicit image or plugin version pins.

### Source excerpt

Hey Falco community, Falco 0.45.2 is available! This patch brings certificate trust updates and newer security dependencies, alongside the reliability fixes delivered in 0.45.1. Since we did not publish a separate announcement for 0.45.1, let's catch up on both releases here. If you are running 0.45.0 or 0.45.1, we recommend upgrading to 0.45.2. And if you are heading to KubeCon in Salt Lake City, we would love to meet you there! The main focus of 0.45.2 is the response to the eMudhra intermediate CA compromise. Clients that still trust the affected certificate chains can accept certificates used to impersonate HTTPS services. Updating the trust stores used by those clients is part of addressing that risk. We refreshed the CA trust stores in both the default Wolfi and Debian Falco images, along with the driver-loader images. The Buster driver loader remains available, with its trust store corrected as well. The release also bundles Falcoctl 0.14.3 and the container plugin 0.7.6, incorporating upstream Go security updates. See the packaging changes for details. For installations using DEB or RPM packages, please apply your distribution's CA certificate updates too. If your deployment supplies a custom CA bundle, make sure that bundle is updated as well. We also updated the bundled OpenSSL to 3.5.9 LTS. There is a compatibility change to keep in mind: its default TLS security level is now 2. RSA, DSA, and DH keys must be at least 2048 bits, and elliptic-curve keys at least 224 bits. Check legacy HTTPS endpoints before upgrading, since weaker keys or parameters can cause TLS connections to fail. The OpenSSL update includes the details. The fixes from 0.45.1 are included too. They address several problems that can interrupt a running Falco deployment or make upgrades harder: Prometheus metrics: fixed a race that could crash Falco when a metrics scrape overlapped with event processing. Details. File output: with keep_alive: true, Falco now reports a failed write and atte

## What are shell vulnerabilities? PHP2Shell, Node2Shell (HTTP2Shell), React2Shell and Log4Shell explained

DevFeed: [What are shell vulnerabilities? PHP2Shell, Node2Shell (HTTP2Shell), React2Shell and Log4Shell explained](<https://devfeed.tech/articles/what-are-shell-vulnerabilities-php2shell-node2shell-http2shell-react2shell-and-log4shell-explained-107251.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/what-are-shell-vulnerabilities>)

Author: Nicholas Thomson

Published: 2026-10-29T19:07:00Z

Content type: article

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [High Profile Threats](<https://devfeed.tech/topics/high-profile-threats.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [2shell-vulnerabilities](<https://devfeed.tech/tags/2shell-vulnerabilities.md>), [ai-vulnerability-discovery](<https://devfeed.tech/tags/ai-vulnerability-discovery.md>), [black-october](<https://devfeed.tech/tags/black-october.md>), [broccoli2shell](<https://devfeed.tech/tags/broccoli2shell.md>), [brotli-vulnerability](<https://devfeed.tech/tags/brotli-vulnerability.md>), [coordinated-disclosure](<https://devfeed.tech/tags/coordinated-disclosure.md>), [cve-2021-44228](<https://devfeed.tech/tags/cve-2021-44228.md>), [cve-2025-55182](<https://devfeed.tech/tags/cve-2025-55182.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cve-2026-111497](<https://devfeed.tech/tags/cve-2026-111497.md>), [http2shell](<https://devfeed.tech/tags/http2shell.md>), [insecure-deserialization](<https://devfeed.tech/tags/insecure-deserialization.md>), [jndi-lookup-injection](<https://devfeed.tech/tags/jndi-lookup-injection.md>), [log4shell](<https://devfeed.tech/tags/log4shell.md>), [node-js-vulnerability](<https://devfeed.tech/tags/node-js-vulnerability.md>), [node2shell](<https://devfeed.tech/tags/node2shell.md>), [out-of-bounds-write](<https://devfeed.tech/tags/out-of-bounds-write.md>), [php-vulnerability](<https://devfeed.tech/tags/php-vulnerability.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [react2shell](<https://devfeed.tech/tags/react2shell.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [shell](<https://devfeed.tech/tags/shell.md>), [shell-vulnerability](<https://devfeed.tech/tags/shell-vulnerability.md>), [unauthenticated-rce](<https://devfeed.tech/tags/unauthenticated-rce.md>), [use-after-free](<https://devfeed.tech/tags/use-after-free.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerabilities-threats](<https://devfeed.tech/tags/vulnerabilities-threats.md>)

### AI overview

Shell vulnerabilities are remote code execution flaws caused when attacker-controlled input reaches unsafe code in underlying libraries, frameworks, runtimes or decoders; the text says these can affect teams even when their own application code is careful, and often require no login. It distinguishes memory corruption bugs PHP2Shell and Node2Shell from logic flaws Log4Shell and React2Shell. PHP2Shell involves use-after-free conditions in PHP request handling; Node2Shell is a Brotli buffer overrun that can affect servers and clients, with code execution demonstrated but inconsistent and crashes or leaks described as likelier. Log4Shell abused Log4j lookups in logged user text, while React2Shell exploited Flight deserialization in React Server Components; both had follow-up fixes after initial patches. The text recommends identifying vulnerable dependencies and container images, upgrading to fixed releases, and tracking ecosystem-specific Brotli patches, which arrive on different schedules. It also describes Aikido scanning, patched images for some versions lacking upstream fixes, and a public-URL checker for PHP2Shell.

### Source excerpt

We explain what shell vulnerabilities are and how to manage them: PHP2Shell, Node2Shell (HTTP2Shell), React2Shell and Log4Shell Category: Guides & Best Practices

## Sizing Red Hat Quay: Profiling components to find real limits

DevFeed: [Sizing Red Hat Quay: Profiling components to find real limits](<https://devfeed.tech/articles/sizing-red-hat-quay-profiling-components-to-find-real-limits-106527.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/10/29/sizing-red-hat-quay-profiling-components-find-real-limits>)

Author: Bala Tripura Bodapati

Published: 2026-10-29T13:01:44Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [architecture-components](<https://devfeed.tech/topics/architecture-components.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [image manifest](<https://devfeed.tech/topics/image-manifest.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [The Julia Language](<https://devfeed.tech/topics/julia.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [components](<https://devfeed.tech/tags/components.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-image-registry](<https://devfeed.tech/tags/container-image-registry.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [customer](<https://devfeed.tech/tags/customer.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [environments](<https://devfeed.tech/tags/environments.md>), [limits](<https://devfeed.tech/tags/limits.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-and-scale-engineering](<https://devfeed.tech/tags/performance-and-scale-engineering.md>), [profiling](<https://devfeed.tech/tags/profiling.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [registry](<https://devfeed.tech/tags/registry.md>), [secure-container-images](<https://devfeed.tech/tags/secure-container-images.md>)

### AI overview

Red Hat Quay has no universal concurrent-pull limit: throughput depends on the whole deployment and must be measured against a documented configuration. In tests using two Quay replicas, NooBaa storage, and 171 MB images, storage endpoints saturated before Quay; increasing them from four to six more than doubled throughput and raised success from 49% to 100%. After storage was scaled, the Python load client became the constraint: its threaded workload hit GIL overhead, and distributing 400 pulls across four client pods improved throughput about 21-fold. At 5,000 concurrent pulls, the test also hit OpenShift's pod PID limit, which the team raised through KubeletConfig and container cgroup settings. The authors recommend profiling each component with observability and treating their results as baselines for that specific setup, not capacity guarantees. Red Hat says it does not currently publish official Quay capacity-planning guidance.

### Source excerpt

Red Hat Quay is a container image registry that stores, distributes, and helps secure container images across on-premise, cloud, and hybrid environments. When a large enterprise customer needed to validate Quay's performance capabilities for their deployment, we turned this sizing request into a systematic method for profiling every component in the architecture. The post Sizing Red Hat Quay: Profiling components to find real limits appeared first on Red Hat Developer.

## The day after tomorrow: After PHP2Shell, it gets worse, then defenders win

DevFeed: [The day after tomorrow: After PHP2Shell, it gets worse, then defenders win](<https://devfeed.tech/articles/the-day-after-tomorrow-after-php2shell-it-gets-worse-then-defenders-win-106472.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/php2shell-day-after-tomorrow>)

Author: Sooraj Shah

Published: 2026-10-29T13:00:00Z

Content type: news

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [human review](<https://devfeed.tech/topics/human-review.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [defender](<https://devfeed.tech/tags/defender.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The excerpt argues that AI can make overlooked bugs in foundational software easier to turn into exploits, as illustrated by PHP2Shell and a Brotli flaw; it reports no mass compromise at the time described. It recommends combining strong security architecture, which limits damage, with rapid remediation. Practical steps include inventorying software dependencies--even those in container and CI images or vendor products--checking code and testing applications and external networks before release and after changes, and routing findings to fixes a person can review. If no upgrade is available or one would break things, it suggests applying the fix to the version already in use. The excerpt says supported PHP versions had fixes and some sites went offline, while warning that the near term could remain difficult.

### Source excerpt

PHP2Shell and Brocolli2Shell may be harbingers of many vulnerabilities to come. But we can be ready Category: News

## The 5 essential layers of AI agent sandboxing on Kubernetes

DevFeed: [The 5 essential layers of AI agent sandboxing on Kubernetes](<https://devfeed.tech/articles/the-5-essential-layers-of-ai-agent-sandboxing-on-kubernetes-106191.md>)

Original publisher: [Read original article](<https://thenewstack.io/ai-agent-sandboxing-kubernetes/>)

Author: Mickey Boxell

Published: 2026-10-29T12:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Overview, News and Trends | The New Stack](<https://devfeed.tech/sources/kubernetes-overview-news-and-trends-the-new-stack.md>), [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [agent-sandbox](<https://devfeed.tech/tags/agent-sandbox.md>), [agent-sandboxing](<https://devfeed.tech/tags/agent-sandboxing.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cluster-security](<https://devfeed.tech/tags/cluster-security.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [code](<https://devfeed.tech/tags/code.md>), [community](<https://devfeed.tech/tags/community.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data](<https://devfeed.tech/tags/data.md>), [egress](<https://devfeed.tech/tags/egress.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [model](<https://devfeed.tech/tags/model.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [security](<https://devfeed.tech/tags/security.md>), [sponsor-cncf](<https://devfeed.tech/tags/sponsor-cncf.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>)

### AI overview

The article recommends building agent sandboxing across five layers: runtime isolation, worker-node setup, access controls, Kubernetes pod requests, and agent sessions. For isolation, runc shares the host kernel and offers performance; gVisor mediates system calls through its user-space Sentry but may constrain applications; Kata Containers use a guest kernel and hardware virtualization for stronger separation, with added resource and maintenance costs. The article also advises default-deny network egress, short-lived task-scoped credentials, limited writable storage, and separate authorization for remote tools. Kubernetes RuntimeClass lets selected pods choose a configured runtime and declare measured resource overhead. For intermittent work, the Agent Sandbox project provides stateful single-pod environments, persistent storage, and options such as warm pools, while leaving isolation to RuntimeClass.

### Source excerpt

An AI agent given autonomy to run code will inevitably run code no human has reviewed. It may install model-selected The post The 5 essential layers of AI agent sandboxing on Kubernetes appeared first on The New Stack.

## Ghost in the PHP2Shell: Why coordinated disclosure and patching will start moving faster

DevFeed: [Ghost in the PHP2Shell: Why coordinated disclosure and patching will start moving faster](<https://devfeed.tech/articles/ghost-in-the-php2shell-why-coordinated-disclosure-and-patching-will-start-moving-faster-105779.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/ghost-php2shell-coordinated-disclosure-faster>)

Author: Dania Durnas

Published: 2026-10-29T04:44:47.605032Z

Content type: opinion

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>)

### AI overview

PHP2Shell illustrates how AI-assisted vulnerability discovery and exploit development can compress response timelines: Calif and Wiz independently found the flaws, Aikido's AI Code Analysis rediscovered one within hours, and Trail of Bits built an exploit with Codex in a day. Leaked CVE identifiers prompted PHP to move its coordinated patch release forward, but the article reports exploitation attempts before the public pre-announcement and widespread attempts afterward. Shorter, tighter embargoes may reduce leak exposure, while giving downstream distributors, hosting providers, and protective services less time to prepare; Cloudflare, with advance notice, had WAF rules ready before the patch. As of October 27, Censys counted about 11.2 million PHP services on fixed versions and 32.5 million still affected among those reporting versions, with over 60 million not reporting a version. The article advises teams to inventory runtimes and dependencies, use timely incident sources that provide mitigations and deployable fixes, prepare for rapid patching, and lock dependencies rather than automatically upgrading everything. It describes Aikido's backported fixed images as one way to patch

### Source excerpt

PHP2Shell showed how fast AI turns a bug into an exploit. Here's why the disclosure should never happen this way again, and why it will anyway. Category: News

## Vercel Container Registry now supports 2 GB compressed image layers

DevFeed: [Vercel Container Registry now supports 2 GB compressed image layers](<https://devfeed.tech/articles/vercel-container-registry-now-supports-2-gb-compressed-image-layers-105509.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-container-registry-now-supports-2-gb-compressed-image-layers-new>)

Author: Andy Waller

Published: 2026-10-28T09:32:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [docker](<https://devfeed.tech/tags/docker.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [layers](<https://devfeed.tech/tags/layers.md>), [link](<https://devfeed.tech/tags/link.md>), [login](<https://devfeed.tech/tags/login.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [toolchains](<https://devfeed.tech/tags/toolchains.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Container Registry now accepts compressed image layers up to 2 GB, up from 500 MB, so larger layers can be pushed without splitting them. The total image size limit remains 15 GB. This helps with images containing large toolchains or dependency sets, including custom Vercel Sandbox environments for coding-agent evaluations. To build and push, install Docker and the Vercel CLI, then run the supplied link, login, and build-and-push commands from the directory containing your Dockerfile.

### Source excerpt

Vercel Container Registry now supports up to 2 GB per compressed image layer, up from 500 MB, allowing larger layers to be pushed without splitting them. The total image size limit remains 15 GB. The higher layer limit is useful for images with large toolchains or dependency sets, such as custom Vercel Sandbox environments for coding-agent evaluations. With Docker and the Vercel CLI installed, run these commands from the directory containing your Dockerfile: Read the Vercel Container Registry getting-started guide to build, push, and pull your first container image. Read more

## This Shit is Hard: Nobody has ever been pwned by Helvetica...or have they?

DevFeed: [This Shit is Hard: Nobody has ever been pwned by Helvetica...or have they?](<https://devfeed.tech/articles/this-shit-is-hard-nobody-has-ever-been-pwned-by-helvetica-or-have-they-105768.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/this-shit-is-hard-nobody-has-ever-been-pwned-by-helvetica-or-have-they>)

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard os](<https://devfeed.tech/topics/chainguard-os.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [2](<https://devfeed.tech/tags/2.md>), [2005](<https://devfeed.tech/tags/2005.md>), [2015](<https://devfeed.tech/tags/2015.md>), [2019](<https://devfeed.tech/tags/2019.md>), [2020](<https://devfeed.tech/tags/2020.md>), [2022](<https://devfeed.tech/tags/2022.md>), [2023](<https://devfeed.tech/tags/2023.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [fonts](<https://devfeed.tech/tags/fonts.md>), [pwned](<https://devfeed.tech/tags/pwned.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security](<https://devfeed.tech/tags/security.md>), [source](<https://devfeed.tech/tags/source.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [this](<https://devfeed.tech/tags/this.md>), [this-shit-is-hard](<https://devfeed.tech/tags/this-shit-is-hard.md>)

### AI overview

Fonts are executable, complex data parsed by historically vulnerable software, yet many Linux distributions ship upstream font binaries without building them from source. Chainguard OS rebuilt 2,347 files across 323 families from available sources, while 205 files in 17 packages remain prebuilt because no sources exist. The work exposed stale or incorrect upstream binaries, packaging and build bugs, and architecture-dependent output differences. Chainguard added lint rules requiring documented exceptions and tracking issues, plus upgrade and rendering checks to compare rebuilt fonts with releases. The article frames direct exploitation through a poisoned distribution font as low probability, requiring both a compromised release and an unpatched renderer, and reports no known cases of distribution font poisoning. Its stronger benefits are provenance, verifiability, and the ability to fix neglected fonts; rebuilding remains difficult where sources, reliable toolchains, or maintainers are lacking.

### Source excerpt

Fonts are an overlooked software supply chain risk. Learn how Chainguard rebuilt thousands of fonts from source to improve security and trust.

[Next page](<https://devfeed.tech/topics/container-images.md?cursor=WyIyMDI2LTEwLTI4VDAwOjAwOjAwKzAwOjAwIiwgImUxZDk2OTFiLTQ2NzItNDQwZC1hMmYxLTNhYjIxZThiNmJlNyJd>)