live wire
▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · OpenShift Service Mesh 3.4.3 restores strict enforcement of OpenShift TLS cipher profilesRed Hat release notes▸SECURITY · Red Hat rated Keycloak password-reset account takeover flaw Critical (Aug. 18)Red Hat Product Security▸PLATFORM · Red Hat previews RHEL CoreOS 10 on OpenShift 4.22 and plans staged mixed-OS migrationRed Hat▸SECURITY · OpenShift 4.15.70 fixes Important-rated vulnerabilitiesRed Hat Product Errata▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · OpenShift Service Mesh 3.4.3 restores strict enforcement of OpenShift TLS cipher profilesRed Hat release notes▸SECURITY · Red Hat rated Keycloak password-reset account takeover flaw Critical (Aug. 18)Red Hat Product Security▸PLATFORM · Red Hat previews RHEL CoreOS 10 on OpenShift 4.22 and plans staged mixed-OS migrationRed Hat▸SECURITY · OpenShift 4.15.70 fixes Important-rated vulnerabilitiesRed Hat Product Errata
upstreambeat.ai
analysisAI

OpenShell 0.1.5 makes sandbox policy and audit data operational

The release gives Kubernetes operators explicit control over pod metadata, adds standards-based OCSF export and hardens failure paths around sandbox policy enforcement.

By The News Desk· Oct 23, 2026the quick take — two AI hosts go live when you do

OpenShell 0.1.5 turns two parts of agent sandboxing that are easy to leave implicit—Kubernetes metadata and audit export—into operator-controlled interfaces. The release changes mechanics that platform teams must configure and monitor when OpenShell runs sandboxed workloads.

Kubernetes metadata becomes an allowlist

Sandbox templates can no longer set arbitrary Kubernetes pod labels or annotations. An operator must now permit each key through allowed_pod_labels or allowed_pod_annotations under the Kubernetes driver configuration. Direct API and SDK callers that populate template metadata are affected, including recovery of timed-out sandboxes; OpenShell's own CLI metadata labels are not.

That is a meaningful policy boundary. Labels and annotations are commonly consumed by admission controllers, service meshes, monitoring systems and internal automation. Requiring an operator allowlist prevents a sandbox creator from silently attaching metadata that activates platform behavior outside the sandbox policy itself. OpenShell also reserves the internal.openshell.ai/ annotation prefix: the gateway rejects those keys on sandbox creation and configuration updates.

The release notes make this an upgrade task, not just a new option. Existing templates that set metadata can now fail until their keys are explicitly approved. Operators should inventory SDK and direct-API callers before rolling out 0.1.5.

OCSF moves from local files toward the telemetry pipeline

OpenShell can now export Open Cybersecurity Schema Framework events as OTLP log records. Traces and OCSF events may use separate OTLP endpoints, while existing configurations with a single endpoint continue to work. The gateway also emits OCSF Authentication events for rejected requests, carrying the mechanism, reason category, peer address and request ID.

For security teams, that makes a denied sandbox request correlatable with the rest of an observability stack instead of leaving it only in an OpenShell-specific sink. The release also fixes the required device.os.type_id field so events validate against OCSF 1.8.

There is one collector migration detail: supervisor audit files now use openshell-ocsf.YYYY-MM-DD.jsonl rather than a .log suffix. Old files are not migrated and may be removed, so collectors must update their globs and preserve any history needed before upgrade.

Enforcement fails closed

Several changes reinforce the same operating model. The network broker now denies an operation when it cannot verify a descriptor rather than falling back to native handling. Hostname-based network policy is tied to supervisor-controlled DNS. OpenShell also publishes a versioned Sandbox Protocol for independently implemented backends, replacing the previous bootstrap descriptor field for external compute drivers.

The practical result is not a new agent framework. It is a more explicit contract between sandbox users, Kubernetes operators and security telemetry systems. Teams adopting 0.1.5 should test that contract in admission policy, metadata-dependent automation and observability pipelines before a production rollout.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk