Jimbow retweeted
nginx2root / CVE-2026-123007: our take after reading the Xint and Wiz writeups
Two teams independently built working unauthenticated RCE exploits against nginx. F5 confirms the bugs, and fixes are out (1.31.9 / 1.30.7). This is a serious one. Patch.
But the version number alone doesn't tell you whether a server is exposed.
The widely quoted "98.9% of nginx hosts are in the affected range" counts version strings. The two critical bugs (CVE-2026-123007, CVE-2026-123633) sit in the HTTP/2 code. They can only be reached if HTTP/2 is enabled, and nginx doesn't enable it by default.
A server is exposed to them when all of this is true:
- nginx 1.9.5 to 1.31.8 (stable branch: up to 1.30.6), without a vendor backport
- HTTP/2 module compiled in (true for most distro packages)
- HTTP/2 enabled on a listener an attacker can reach
Check from outside:
curl -sI --http2 -o /dev/null -w '%{http_version}\n' https://HOST/
"2" means HTTP/2 is on, "1.1" means it's off. Test the nginx itself, not a CDN in front of it.
Check on the server:
nginx -v
nginx -V 2>&1 | grep -o with-http_v2_module
nginx -T 2>/dev/null | grep -E 'listen.*http2|http2 +on'
No output from the last command means HTTP/2 is not enabled.
How common is HTTP/2 on nginx? We spot-checked a few hundred nginx HTTPS endpoints listed on Shodan: roughly two thirds negotiate it. So not 99%, but still millions of servers.
What to do:
- Update to 1.31.9 / 1.30.7 or your distro's fixed package. Distros backport, so check the advisory, not just nginx -v.
- Can't patch yet? Turn HTTP/2 off until you can.
- The same release fixes three more RCE bugs that need other features (resolver with a variable proxy_pass, HTTP/3, mail proxy). Patching covers those too.
Xint: nginx2root.com/
Wiz: wiz.io/blog/nginx-http2-rce-…
F5: my.f5.com/manage/s/article/K…
Jimbow retweeted
If you are an N ABLE N-CENTRAL ON PREMISES CUSTOMER this is important!
uptime.n-able.com
Neat!
Want your own Slack for $0? I open-sourced Ember. It deploys to @Cloudflare’s free tier in about a minute, works with Slack-compatible payloads, and includes an AI assistant and media attachments.
1
33
Jimbow retweeted
👇👇👇
Cairn: github.com/oritera/Cairn
CyberStrike: github.com/CyberStrikeus/cyb…
PentAGI: github.com/vxcontrol/pentagi
CyberStrikeAI: github.com/AIPentest/CyberSt…
PentestGPT: github.com/GreyDGL/PentestGP…
PentestAgent: github.com/GH05TCREW/pentest…
AutoPentester: github.com/YasodGinige/AutoP…
VulnBot: github.com/KHenryAegis/VulnB…
RedAmon: github.com/samugit83/redamon
MAPTA: github.com/arthurgervais/map…
Strix: github.com/usestrix/strix
Shannon: github.com/KeygraphHQ/shanno…
BugTraceAI: github.com/BugTraceAI/BugTra…
Nebula: github.com/BerylliumSec/nebu…
hackingBuddyGPT: github.com/IPA-Lab/HackingBu…
HexStrike AI: github.com/0x4m4/hexstrike-a…
CAI, now archived: github.com/aliasrobotics/CAI
Beyond #Artex, what other #offensive #AI frameworks should the cybersecurity community be watching?
A few on my radar:
🔹 CyberStrike
github.com/CyberStrikeus/cyb…
🔹 Cairn
github.com/oritera/Cairn
🔹 PentAGI
github.com/vxcontrol/pentagi
Have you tried any of these? Let me know!
Jimbow retweeted
With the recent wave of vulnerability disclosures, it’s a good time to take a closer look at your own code.
Turn your coding agent into a team of security auditors with the open-source skill that seeded Cloudflare’s vulnerability discovery harness.
The 6 phase approach:
1. Map the codebase
2. Hunt for vulnerabilities
3. Challenge each candidate
4. Record the findings
5. Verify the findings
6. Report what’s confirmed, rejected, or still needs validation
Start your hunt here:
github.com/cloudflare/securi…
Our security researchers built an autonomous cyber vulnerability discovery, exploitation, and patching pipeline.
In a single run with an upcoming cyber model, it validated and generated patches for 948 local privilege escalation vulnerabilities in the Linux kernel at a total API cost of $1.2 million.
Jimbow retweeted
🚇 Next stop: #BSidesLDN2026!
🎉 THE SCHEDULE IS NOW LIVE!
🎤 3 main talk tracks
🌱 2 Rookie Tracks
🛠️ 10 Hands-on workshops
🐻 8 Villages
Saturday 12 December, Novotel London West.
Start planning your day!
👉 bsides.london/schedule
🎸 No REST 'til Hammersmith!
Jimbow retweeted
Replying to @JeremyClarkson
What a man. I will never forget his shoey on the podium. Cheers!
Jimbow retweeted
Patrick Stewart. Turned up so early and so unobtrusively to be a star in the reasonably priced car, we mistook him for a delivery driver and asked him to go round the back. Took his hat off and said, “But I’m the captain of the Enterprise”. Fucking nice guy.
Jimbow retweeted
Total hacked is around $3.5B now across multiple chains…
Yet unconfirmed, but possibly there is a massive binance hack happening right now.
It looks like a @binance wallet has been drained into new address. Contract call was funded by Tornado Cash.
TX hash: 0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3
Jimbow retweeted
Discord is making messages from public servers discoverable on search engines like Google starting this November.
Server admins can opt channels out starting today.
Users can opt out of sharing their messages in settings -> Data and Privacy.
Jimbow retweeted
I've led vulnerability management for some very large companies. I've been in the trusted embargo 0day info sharing rooms.
I think it would be negligent at this point to assume that they will be the norm moving forward.
We can't expect to get a nice coordinated vuln announcement and patch handed to us in private with weeks to handle it.
We need layers of defense so 0days in internet facing devices won't be catastrophic. We need machine speed detections and response.
And of course we need to figure out the new norm of how we handle 0days in hours not days. This will take agents and harnesses you might not have yet.
A lot of this has been true for a while, but you could get away with handling in fire drill mode when happened and put off the actual engineering.
As people are saying, the interest rates on security tech debt just skyrocketed.


































