CVE-2026-84445Disclosure

LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

0.5/ 10 priority

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Patch or workaround signal is available
  • 4 mentions across 3 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 1 signal
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 2 mentions (2026-09-12); latest day: 1
  • 4 total mentions across 3 days

Deep dive

Activity timeline4 mentions / 3d
01122Mentions · 2026-09-09: 1Mentions · 2026-09-12: 2Mentions · 2026-10-15: 1Patch / Workaround · 2026-09-12: 2Technical Details · 2026-09-09: 109-0909-1210-15
Signal classification2 categories
Disclosure
250.0%
Patch
250.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-09-091
Disclosure1
2026-09-122
Patch2
2026-10-151
Disclosure1
Full discourse4 posts
  • Repojournal@repojournal
    Patch

    Two Kubernetes feature gates are gone: MultiCIDRServiceAllocator and DisableAllocatorDualWrite have been removed. gRPC gets bumped to v1.82.2 in pod-security-admission, and the branch it came in on references grpc-cve-2026-84445. Elsewhere: a fix marks invalid all-device allocation as a per-node failure in dynamic-resource-allocation. ktesting got its implementation code reorganized (doc․go, tcontext․go, assert․go, signal*.go) to make the source readable top-to-bottom. #kubernetes https://repojournal.com/showcase/kubernetes/2026-09-12/service-cidr-feature-gates-retired-grpc-bumped-to-1-82-2

    Post summary

    Kubernetes updated its codebase by removing two feature gates, bumping gRPC to version 1.82.2 to address grpc‑cve‑2026‑84445, and applied a fix to mark invalid all‑device allocations as per‑node failures, signifying a patch release.

    03050196
    452 followersView on X
  • Repojournal@repojournal
    Patch

    Kubernetes is bumping google․golang․org/grpc to v1.82.2 across kubernetes/kubernetes and dynamic-resource-allocation, tagged against CVE-2026-84445. The dependency lands in both repos. If you track either, that's the change to pull. Elsewhere, kubeadm gets a bug fix: ServiceIsEnabled was matching on the whole rc-update show output instead of the service and runlevel columns, which broke OpenRC enablement detection. And in DRA, an invalid all-device allocation is now marked as a per-node failure. #kubernetes https://repojournal.com/showcase/kubernetes/2026-09-12/service-cidr-feature-gates-retired-grpc-bumped-to-1-82-2

    Post summary

    Kubernetes teams patched CVE-2026-84445 by bumping google.golang.org/grpc to v1.82.2.

    03040177
    452 followersView on X
  • GCP Weekly@gcpweekly
    Disclosure

    CVE-2026-56859 CVE-2026-56860 CVE-2026-56862 CVE-2026-56864 CVE-2026-56865 CVE-2026-81870 CVE-2026-84303 CVE-2026-84304 CVE-2026-84445 N/A Security fixes for apigee-mart-server. This addresses the following vulnerabilities: CVE-2024-6763 CVE-2025-46392 CVE-2026-10050 7/16

    Post summary

    The text announces security fixes for apigee-mart-server addressing multiple CVEs but provides no technical details, exploit references, or specific patch naming.

    1000025
    1.8K followersView on X
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨HIGH - gRPC-Go xDS Routing Panic DoS via Missing Host/:authority (CVE-2026-84445) In gRPC-Go servers using xds.NewGRPCServer(), an HTTP/2 request missing both :authority and Host triggers an index-out-of-bounds panic in the xDS routing interceptor; the per-RPC goroutine doesn’t recover, crashing the whole process (DoS). Non-xDS servers are not impacted. 👉Affected: http://google.golang.org/grpc (gRPC-Go) with xds.NewGRPCServer() enabled

    Post summary

    The post announces a high‑severity CVE‑2026‑84445 in gRPC‑Go's xDS routing interceptor, describing how a missing :authority header can cause a panic and a denial‑of‑service. No exploit, PoC, patch, or evidence of active exploitation is referenced.

    0000084
    304 followersView on X

Explore more