Friday Security Briefing Kickoff

SPEAKER_00 0:00

Here's your briefing for Friday, august seventh, twenty twenty six.

Linux SCTP Bug And Container Escape

SPEAKER_00 0:03

Tencent researchers disclosed SCTP Ain't them, a use after free in the Linux kernel's SCTP networking stack that has existed since two thousand eight. With SCTP reachable on the target, it yields full route and lets attackers escape containers to the host. The bug was assigned CVE twenty twenty six-six four five six six six six six six four and fixed and stable kernels released august third. No public exploits were known at disclosure. The flaw affects Debian, Ubuntu, Rocky, and RHEL builds among others. Exposure is limited because it requires local access and SCTP enabled, but the age of the bug and the container escape path make it worth attention for any environment running older kernels with that protocol in use. That's the headline from the Hacker News, and the real story is how long these issues can hide in plain sight. Eighteen years is not a patch cycle, it is a career.

Natjack And NAT Session Hijacking

SPEAKER_00 0:49

Security researcher Malcolm Stag presented Natjack at Black Hat USA showing how attackers with privileged access behind the same NAT can manipulate connection tracking tables to hijack active TCP sessions, spoof DNS responses, expose internal ports, and exhaust NAT resources. Separate CVEs landed in Windows, Hyper-V, NAT, and Linux NetFilter contract. The attack does not require a universal patch because it exploits fundamental behavior across implementations. Defense is center on isolating untrusted workloads from shared NAT infrastructure and applying the available Windows and Linux updates. That's the headline from the Black Hat presentation, and it is a reminder that the plumbing we rely on for isolation has always been more porous than the diagram suggest.

GitHub Issues Trigger CI Runner Code

SPEAKER_00 1:30

Novi security showed that a GitHub issue created by an unprivileged account was enough to execute code on the CI runners for Anthropics and Google's own coding agent repositories. On opening I setup, it could hijack the next agent run. The Gemini CLI carried CVE twenty twenty six-12537, a command injection via a crafted dash NAV file that ran before the sandbox. Claude code leaked an API key one character at a time through a download counter. Both are now patched. The attack path bypassed the model entirely in several cases. Public issues became direct execution channels into the build environment. That's the headline from the Black Hat disclosure. And the uncomfortable part is that the vendors own agent tooling shipped with these gaps. If the builders cannot keep their CI safe from a GitHub ticket, the rest of us should assume the defaults are not our friends.

Meta Hit With New Penalties

SPEAKER_00 2:15

A New Mexico court added five hundred sixty seven million dollars to Meta's penalties in an ongoing child safety case. The ruling comes amid broader scrutiny of platform safety practices and follows other large settlements and regulatory actions. The scale of the judgment keeps the pressure on social platforms to demonstrate meaningful controls rather than process theater. Whether the money changes design incentives remains the open question. That's the headline from TechCrunch, and the number is large enough to notice even for a company the size of Meta, regulators are still willing to write big checks when the underlying conduct does not improve.

Microsoft 365 Phishing With Proxies

SPEAKER_00 2:47

Arctic Wolf Labs reported a widespread adversary in the middle phishing campaign against Microsoft three hundred sixty five accounts. The actors use residential proxies to blend in, maintain sessions on roughly eight hour cycles, and focus on harvesting payroll and finance related messages. The activity overlaps with Microsoft's Storm two hundred seventy five cluster and has hit healthcare, education, manufacturing, government, and professional services organizations in multiple countries. The campaign is financially motivated and relies on account takeover rather than novel malware. Standard MFA and session hygiene remain the primary defenses. That's the headline from the Hacker News. And the pattern is familiar. Once the account is in, the attacker lives off the land in the mailbox. The residential proxy layer just makes the initial compromise harder to spot in the logs.

Five Stories One Shared Lesson

SPEAKER_00 3:31

Five stories, one consistent signal. Old kernel code still bites. New attack classes exploit the plumbing everyone assumes is solid, vendor agent tooling ships with execution paths that should not exist. Courts continue to price safety failures in hundreds of millions, and the fishing campaigns that succeed are the ones that look like normal traffic. The surface keeps growing, the fundamentals of isolation, authorization before execution, and basic hygiene have not

Closing Advice And Signoff

SPEAKER_00 3:55

kept pace. That's the briefing. Stay sharp, patch your systems, and we'll see you tomorrow.