@Sagarvd01@wiz_io@xint_official@MetnirAI@rapid7@ikotas00 That's the documented stopgap for both CVE-2026-123007 and CVE-2026-123633. Apply it on the nginx that accepts the client HTTP/2 connection, including ingress images with a bundled binary. Those will lag 1.30.7/1.31.9, so disable HTTP/2 until the controller image updates.
@k2_naka@ikotas00@OpenAI@grok Yes. It already shipped. F5 released 1.31.9 (mainline) and 1.30.7 (stable) today, ahead of the old Dec 9 date. Those fix both HTTP/2 RCEs (CVE-2026-123007 and CVE-2026-123633). If your distro package isn't out yet, set http2 off; and remove http2 from listen.
Keeping up with vulnerabilities shouldn't mean checking five databases to understand one CVE.
We built Fencer Intel to bring major advisory sources into one feed, with exploitation context from KEV, EPSS, and public exploits.
Check your lockfiles, follow updates, connect your AI coding agent through MCP, or plug the data into your own tools.
Free. No account or API key.
Try it out and let us know what you think: https://t.co/hUjrfu3eZC
Tons of conspiracy theories right now about cyber attacks or preventing cyber attacks being the cause of the recent major infra issues in the US.
We at @fencer_security have been paranoid for a while. It’s why @ivankriznar built a usable intelligence feed for everyone vibe coding to help secure what they’re building.
What was initially a weekend project turned into something much bigger with near realtime data, alerting, MCP and API access as well as skills and tools to help you protect your work.
Please try it out and let me know what you think!
If you run PHP anywhere, patch it today.
Two RCE bugs in PHP core, CVE-2026-109618 and CVE-2026-109619, both 9.2. Reportedly, every release from 5.4 up is affected. Fixes shipped this afternoon (UTC):
8.5 → 8.5.12
8.4 → 8.4.27
8.3 → 8.3.36
8.2 → 8.2.35
8.1 and older get no official release. Check your distro or LTS vendor for backports, or upgrade.
Two things people are getting wrong 👇
1/ Plenty of companies run PHP without thinking of themselves as a PHP shop. WordPress is PHP, and so is that admin panel, that status page, and the staging box nobody decommissioned. Check every host you own that answers to the internet, including the ones nobody has logged into in a year.
2/ The risk went up sharply when the patch landed (30 mins ago!). Details leaked yesterday, and a few attackers already had them. Cloudflare saw attack traffic at 07:43 UTC, hours before any fix was made public. Now the patch points everyone at the exact bug, and writing an exploit from a diff is a short job.
If you can’t patch in the next few hours, Cloudflare’s WAF rules block the known attack patterns, including on the free plan. They only help if traffic actually goes through Cloudflare, and attackers are already tweaking payloads to get past them. That buys you hours, so spend them patching.
🚨Python friends, upgrade (or have your agent upgrade) every certifi package across all your projects and machines!
uv self update
uv lock --upgrade-package certifi
Private keys from 8 intermediate CA certs have been compromised!
https://t.co/ro5N4SQPO3
Some other things to upgrade:
* Go: 1.27.3 or 1.26.10, then rebuild your Go programs
* rustls-webpki: 0.103.16
* webpki-roots / webpki-root-certs: 1.0.10
* Electron: 44.9.1, 43.8.1 or 42.11.16
* NSS: 3.131.1
* Firefox: 158.0.1 (ESR: 153.5.1 or 115.43.1)
* Ubuntu ca-certificates: 20260816ubuntu0.<release>.1 (for 22.04, 24.04, 26.04 and 26.10)
* Homebrew ca-certificates: 2026-09-25_1
* Chrome, Apple, Windows: nothing to do, they’re blocked automatically
Still waiting for a fix:
* Debian ca-certificates: disable the two roots by hand
Node.js
* Composer ca-bundle
* macOS /usr/bin/curl: remove the two roots from /etc/ssl/cert.pem by hand
SOC 2 requires a pen test. Most teams spend weeks waiting for results, then more time figuring out what to do with them. Gabriel Garayalde ran his with Fencer and had findings he could act on the same day.
"Will my auditor accept an AI pen test?"
SOC 2 doesn't prescribe methodology. Auditors judge the report: scope, recognized methodology, severity-rated findings, and proof each one is exploitable.
Fencer's AI pen testing reports document the full attack path, the fix, and the retest that confirmed closure.
Learn more here: https://t.co/ZzUFzp7iLZ
The slowest part of your SOC 2 just got a lot faster. Now you can run a full pen test on demand, and get results in hours.
We just launched Fencer AI pen testing. Scope a pen test in the morning, read the audit-ready report the same day. Network and domain scanning run continuously alongside it. $3,000 a year.
https://t.co/ZzUFzp7QBx
WordPress just went from bad to worse.
wp2shell now has two CVEs and a public working PoC.
One breaks REST batch routing. The other injects SQL. Chained together, they allow unauthenticated RCE on affected WordPress sites.
Update to 6.9.5 or 7.0.2 now.
Can’t update yet? Cloudflare WAF can mitigate the attack while you patch.
Check your site: https://t.co/VOoHl57skR
Official release:
https://t.co/B0YcUMbK8i
SOC 2 gets you in the door. It doesn't get you through procurement’s security questionnaires.
Most enterprise buyers treat SOC 2 as table stakes now. Their security teams trust the evidence more than the badge, and their questionnaires dig into specifics a clean report often misses: key custody, retention, vendor risk, pen-test cadence.
We built a free check that reads your SOC 2 the way an enterprise security reviewer would, and shows where you'd fall short before the buyer does.
Upload your report, name who you're selling into, get a gap report in about 90 seconds.
https://t.co/u7ugyaMIgM
An honest list of where startup security hours actually go:
⌛️ Exporting CSVs from four different tools and cross-referencing them in a master spreadsheet.
- Tuning alert rules to filter out the same false positives you filtered out last month.
⌛️ Retroactively producing audit evidence for processes the team is already doing.
⌛️ Filling out 300-row security questionnaires from enterprise prospects.
⌛️ Babysitting tools.
Based on his experiences as a startup CTO, our co-founder Tim wrote a field guide on what to do about all of it.
https://t.co/t0Cy0TIMU4
There's a name for the stack most startups assemble to get to SOC 2.
The duct-tape stack.
A free vulnerability scanner. The GRC platform. GitHub built-ins. A CSPM tool you bought separately. Endpoint coverage from somewhere else. Alerts forwarding to Slack. The weekend audit-prep ritual.
It works. It got you here.
The trouble is what's underneath: every sprint, your team is making invisible trade-offs to keep it running.
Fencer is full-stack security for startups. One platform, built for the stage you're at, and the next.
https://t.co/kFB9OopNc7
"As CTO, you're the de facto CISO until you're big enough to hire one, whether you like it or not."
From the intro of Tim's new startup security field guide.
He's been in that seat: he was CTO of Zenput before he co-founded Fencer, and he built the security program, ran SOC 2, and figured out the operations himself.
His guide is for the CTO who's running security on top of everything else.
https://t.co/t0Cy0TJkJC
Free SAST tool.
Dependabot.
GitHub Advanced Security.
The GRC platform you bought for SOC 2.
A separate CSPM.
Endpoint coverage from a different vendor.
Alerts forwarding through Slack.
The weekend audit-prep ritual.
If this is your stack, you're not alone. And you've probably outgrown it.
https://t.co/kFB9OopNc7
When 90% of your security hours go into deciding what to fix rather than fixing it, your stack is generating work, not finishing it.
Here's four signs your startup's security stack has hit its limit.
https://t.co/wYYPKtUikI