🚨 CRITICAL: GitLab flaw (CVSS 10.0) affects 12 years of releases. CVE-2026-110264 could allow unauthenticated remote code execution on self-managed servers. Read - thehackernews.com/2026/10/cr…

Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.

🚨 10:00 AM ET: A 15-MINUTE BATTLE FOR THE ENTIRE INTERNET BEGINS. Today, a critical zero-day vulnerability (CVSS 9.2) in PHP—the backbone running nearly 80% of the web—goes public at 10:00 AM ET / 7:00 AM PT. Forget the technical jargon. Here is what actually happens: The second the patch drops, hackers will use AI to reverse-engineer the fix in seconds and unleash automated exploits worldwide within 15 minutes. This is not just a problem for developers. When e-commerce sites, apps, and platforms collapse, your leaked home address, passwords, and credit card numbers flood the dark web. ⚔️ The brutal reality today: Engineering teams deploying patches in minutes vs. Oblivious companies gutted before lunchtime. 🛡 3 things you must do to protect yourself right now: 1. Turn on Two-Factor Authentication (2FA) across all critical accounts. 2. Stop password reuse immediately. 3. Beware of fake "emergency password reset" phishing emails flooding inboxes today. Cyber warfare changes forever this morning. Bookmark and share this to keep your team and family safe.

The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2. PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.

The TiDB leaks fulcrumsec.vg/pingcap/

Apple should REALLY add a sliding dock to iOS so we can fit more apps. How is this not a feature yet? 😭

iPhone Duo: First impressions from someone who’s been using it for a week! The good: • “Best foldable by far.” • The speakers are incredible. • One of the biggest surprises is typing on the unfolded screen in portrait mode. The keyboard is so comfortable that he says he could write 5000 word essays on it. The bad: • Touch ID feels like a real step backward. • Most apps look terrible and need updates. • The cameras are a downgrade. (compared to the iPhone 18 Pro Max?) What’s interesting is that he’s now using the iPhone Duo 90% of the time, switching back to his iPhone 18 Pro Max for the remaining 10%. Apple’s support for using two iPhones with one SIM makes this much easier. One more interesting detail is that he believes many people will end up removing the inner display’s nano-texture layer, which he describes as a peelable screen protector. Overall, despite the compromises, he considers it the best foldable he’s ever used.

You have to invent the future. It doesn't just happen.

New on our Engineering blog: Creating in-house source control. In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale. Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…

engineers used to hate context switching and now that's all engineering is

Ben Horowitz: “The most dangerous thing going on in AI is Anthropic and Bill Gates” “Anybody can go say, ‘AI is going to kill us,’ and you'll be on every major news station and every newspaper and so forth. I think it's extremely dangerous, though, when it comes from Bill Gates because he is so credible, because he did build Microsoft, and people think of him that way, and then certainly he's been a big political donor, so he has a lot of political juice, particularly on the Democratic side. The big risk that everybody talks about is that the models are going to recursively self-improve, and then they're going to take off, and then they're going to become so smart and run away from us. Well, what would be the preconditions for that? Ali Ghodsi from Databricks had a great formulation of, ‘Well, what would be the preconditions for that?’ And he had four preconditions. One is that the next model has to require fewer GPUs than the last. The second thing is the next model has to take less time to train. And then the accuracy of the next model has to be better than the last, so it's got to be a better model. And then finally, it's gotta keep happening again and again and again. Zero of those four have been met. We're not on track for any of those four to be met, and so we're really talking about a risk that's entirely theoretical at this point that we're not mapping to.”

Gavin Baker on the other side of Ben's bandwidth story: at the peak of the 2000 bubble, 97% of America's fiber sat dark, and today there are no dark GPUs. "I had, depending on how you look at it, the privilege and the misfortune of being a tech investor during the year 2000 bubble, which was really a telecom bubble." "The year 2000 bubble was defined by something called 'dark fiber.' Dark fiber was literally fiber that was laid down in the ground, and not lit up... At the peak of the bubble, 97% of the fiber that had been laid in America was dark." "Contrast that with today. There are no dark GPUs. All you have to do is read any technical paper, and one of the biggest problems in a training run is that GPUs are melting." @GavinSBaker