Daily Engineering Intelligence

Technology Newspaper

← Back to Home

Engineering Intelligence β€” Sunday

November 1, 2026

πŸ”₯ What Changed

A quiet Sunday with one item. Dapr shipped eleven security fixes across its three supported lines, and the worst of them break its service-to-service identity model: a sidecar could forward another workload's gRPC call under its own mTLS identity. Upgrade if you run Dapr; if you build gateways or meshes in Go, the root causes are worth knowing either way.

Also seen: Hacktron's GNU Savannah write-up (via LWN, 10-31) shows that an email address like ` touch${IFS}/tmp/x@attacker.example gave any registered user code execution on the forge's backend. From there they became superuser, impersonated Bash's maintainer, confirmed they could add an SSH key with push access to upstream Bash, and reached root and a GNU backup server through an unpatched kernel. It was reported to the FSF on May 11. It is fixed now, but it is a sharp reminder that source-forge accounts are part of your supply chain. Parameter Labs' ChatGPT account takeover chained a MathLive postMessage handler that used innerHTML` with a YouTube oEmbed endpoint the CSP allowed, so a shared link could run script as the visiting user. OpenAI has fixed it. Go #82717 (MPTCP on by default): Damien Neild asked why no other platform enables MPTCP for listeners by default, and MPTCP maintainer Matthieu Baerts answered that Linux leaves the choice to applications. Still no decision. No Go, Kafka, NATS, Kubernetes or OCR release was worth a slot overnight.

Holds: Go 1.27.4/1.26.11 (still not pre-announced; go.dev/dl still lists 1.27.3/1.26.10); Go #82717 MPTCP default (no decision); CVE-2026-98432 RHEL/Ubuntu kernels (Ubuntu still shows "Vulnerable"); x/oauth2 CL 854305; Go #82374, #82472, #82497, #82547, #82677, #82682/#82685 unchanged; go-jose v3 fixes; Kafka 3.9.3; GitHub RCAs for 10-21/22/26, 10-28, 10-29 and 10-30; Northflank root cause; Dapr CVE/GHSA IDs. Alternates: Google PageBreak AI security agent (InfoQ), Databricks Lakebase branching for CI/CD, Kubernetes confidential containers with Fortanix attestation, Cloudflare post-quantum Geo Key Manager beta, LocalStack for Azure preview.

Dapr 1.19.1, 1.18.10 and 1.17.19 fix eleven security issues, including sidecars that relayed other workloads' gRPC calls under their own mTLS identity and a Scheduler that handed one app's workflow reminders to any app in the namespace

Dapr (the Go sidecar runtime for microservices on Kubernetes) shipped the same eleven security fixes on all three supported lines. The release notes give no CVE or GHSA IDs. The serious ones break the service-to-service identity model. gRPC relay: each sidecar's internal port (50002) forwarded a proxied gRPC call addressed to a *different* app, and stamped itself as the caller with its own mTLS identity. So any workload with a Dapr identity, in any namespace, could send a call to app B's sidecar addressed to app C. App C's access policy and any caller checks in its code then saw dapr-caller-app-id: B. The sidecar also treated an app with the same ID in another namespace as the local app. Scheduler reminders: WatchJobs checked the caller's app ID but not which actor types it declared, so an app could claim another app's dapr.internal.<ns>.<app>.workflow/.activity types. It then received that app's workflow and activity reminders, including workflow inputs and history, and could stall them by acknowledging without acting or by setting a low concurrency limit. Access-control bypasses: policies matched the invoked method literally, so %61dmin/secret, or admin;x/secret on servlet-style servers, slipped past a deny rule for /admin/secret. This finishes an earlier fix that only covered %2F, %5C and %2E. A percent-encoded health-check path also skipped the API token check. Sentry OIDC: with --oidc-allowed-hosts set and no static --jwt-issuer/--oidc-jwks-uri, X-Forwarded-Host: sentry.example.com:80@attacker.example passed the allowlist and produced a discovery document pointing issuer and jwks_uri at the attacker, cached publicly for an hour. The rest: a Scheduler prefix delete that removed other apps' jobs, unauthenticated, unbounded metadata writes on the public port, sidecar crashes on malformed encrypted state, the outbox accepting forged messages on its internal topic, gRPC servers accepting headers far beyond the configured read-buffer size, and HTTP verb rules ignored for requests without metadata. 1.19.1 and 1.18.10 also fix a Placement reconnect loop that leaked a gRPC connection (about 8 goroutines a second) on every failed attempt. 1.18.10 additionally fixes workflows that became permanently unrecoverable after a save with a timer in the inbox.

Why you care: This is a clean lesson in how sidecar meshes go wrong. mTLS proves which *hop* is talking to you, not who started the call. A forwarder that re-signs requests with its own identity turns every allowed caller into a confused deputy, and a path policy that matches bytes before the app's router decodes them is only a suggestion. If you run Dapr, upgrade to the patch for your line. Note the breaking change: PUT /v1.0/metadata/{key} on the public port now returns 404, so move any such calls to the main HTTP API port. If you use Sentry's OIDC server, set --jwt-issuer and --oidc-jwks-uri statically. Also prefer allow-list policies (defaultAction: deny) over deny-lists. Even without Dapr, the same checks apply to any Go gateway or service mesh you build: decode the path exactly once, the way the downstream router will, before you authorize it; carry the original caller's identity end to end instead of re-deriving it at each hop; and never build an OIDC issuer from a request header.
Read the Dapr 1.19.1 release notes β†’

πŸ“š Worth Your Time

Nothing cleared the bar for a long read today.