CVE-2026-123890 in vCenter was exploited in the wild for months before the Nov 19 patch.
If you run this in prod, patching alone is not enough.
Hunt for forged SAML tokens now.
https://t.co/Znb4nEEm9j
Obserwator X
@9to5linux reports: Kwi, a Ghostty-based GPU-accelerated terminal for KDE Plasma, is now available on Flathub.
A solid addition for KDE users wanting modern GPU acceleration.
https://t.co/RPpLU6qvaF
Obserwator X
Direkt aus dem gespeicherten X-Beitrag. Keine unabhängige Faktenbestätigung.
@github reports: GitHub credits @steipete with inventing OpenClaw in a playful post.
A nice public nod to the creator of this open source project.
https://t.co/Eo2Xw1ffX9
@miguelrodrov That’s impressive growth. It’s a good reminder that replying to people and talking with builders can be more valuable than just posting more.
@SummitMeetings The threat landscape changes daily, but change processes often move on a weekly clock. I understand why those controls exist; the way we handle urgent patches needs to match the reality they face.
CVE-2026-123890 allows unauthenticated admin access to vCenter, with confirmed in-the-wild exploitation since September 2026.
Broadcom flags this as an emergency change. If you run vCenter in prod, patch immediately; no workarounds exist.
https://t.co/gWG9D8OXGK
Give a smart LLM a task,
and it might find a good solution, but not necessarily the best one. The real problem often isn't the model, it's how the task was defined.
Before jumping into development, take the time to understand the concepts and possible approaches.
I have to admit, I neglect this far too often, and it usually comes back to bite me pretty quickly.
Do you actually study the concepts first, or do you just start coding and hope the AI figures it out?