Want to become an ethical hacker? ๐ฅท Here's a list of my favourite [mostly practical] resources ๐
They are all free (or have a free option) and there's more high quality material here than anybody realistically has the time to complete โณ
We helped FFmpeg find and fix 21 security vulnerabilities.
In a 1.5M-line codebase, we spent just $1K in API costs. Some of these bugs had been hiding for decades.
We also developed a PoC demonstrating an RCE primitive when FFmpeg processes RTSP streams.
Full write-up: https://t.co/mIrjirCgcB
@Hacker0x01 The words "train", "fine-tune" or "improve" generative AI models also leaves a lot of room. Most companies don't use data to "train" models, they give standard models (e.g. Opus) access to data, tools etc.
@Hacker0x01 "Researcher submissions" leaves room for all kinds of legal tricks. What do you actually use for training? Any anonymised data that was once a part of a report? Presumably if all the training data was publicly sourced, you'd be quick to confirm that ๐
@h4x0r_dz They are probably being legally accurate when they say they train on "researcher submissions". Like when the NSA said "nobody is *listening* to your phonecalls" ๐
New @rapid7 observed exploitation of PAN-OS GlobalProtect auth bypass vulnerability CVE-2026-0257 which allows authentication bypass cookies to be forged for VPN access. Full details, technical analysis, PoC , IOCs and remediation guidance in the blog: https://t.co/Bye7K5gzKO
4 RCE chains across 4 LiteLLM versions, each patched within days of working.
What started as #Pwn2Own Berlin prep turned into a race against the vendorโs commit log.
https://t.co/OFB7GBIosm
By @bestswngs & @bruce30262
This is required reading today.
@caseyjohnellis didn't even write this today about MSRC - but it nails it.
Full disclosure IS the agreed upon path forward to keep a vendor in check who stonewalls, threatens, or otherwise is shit to work with for security researchers.
Found an unpatched RCE in Gogs ๐ Any authenticated user can get code execution on the server through argument injection into git rebase. Full @rapid7 writeup + @metasploit module available now!
๐https://t.co/VAYLxZ6o1b
I won't keep you in mystery any longer, here's how I found an XSS vulnerability *in* Shazzer!
The chain involved some interesting browser techniques no sane developer could foresee. Check out the details below:
https://t.co/nY20Anz0VO
(and thanks @garethheyes for making Shazzer!)