Found a full-blown CSP bypass on the current version of Firefox (69). Not working on the beta version. PoC: https://t.co/WTQppEnh1s<object data="javascript:alert(1)"></object>
#bugbounty
Saiu o Elytron Talks #02!
Fui o host do papo com o @0xTeles e o fepame sobre como o Bug Bounty cria profissionais pra ataques reais. 👇
https://t.co/FFum5wn0zL
Next.js v16.2.5 fixes a bunch of vulnerabilities reported by @HacktronAI.
Patch ASAP, especially if you’re running self-hosted Next.js that SSRF might affect you
CVE-2026-44574: Middleware / Proxy bypass via dynamic route parameter injection
CVE-2026-44578: SSRF in applications using WebSocket upgrades
CVE-2026-44581: XSS in App Router applications using CSP nonces
@caueobici@girorme1 Historias que seu avo nunca lhe contou sobre firebase - @vrechson & @Highustavo
Imagens sao dificeis - Thumbor 0days - @caioluders
SunCodeQL - Resolvendo a Complexidade do Frontend com SAST - m4z4r0p3
m4qu1n4 d0 mund0.ANS - gld
I began looking into browser security issues again in 2026 and while reviewing extension permission APIs, I noticed that the default declarativeNetRequest API (which only requires permission to block content on all pages) can be leveraged into a side-channel attack.
This permission ends up allowing an extension to infer the full URL of open tabs without requesting the chrome.tabs permission, and it can also leak the full URL of cross-origin redirects.
Unfortunately, fixing this issue has been deemed unrealistic by Chrome, and the risk has been accepted, so it is worth keeping this in mind when granting content-blocking permissions to browser extensions.
The complete public report can be found at https://t.co/CI8miz1lL4.
🚨 CFP aberto — Bug Bounty Village @ H2HC 2025 🚨
Achou um bug insano, bypass criativo ou tem case real de pentest/bug bounty?
Manda sua talk!
👉 https://t.co/qiinfEVgtH
#H2HC#BugBounty#Call4Papers#HackerCulture
Securing @gumroad with Hacktron AI
Three months ago, Hacktron was still early. @HacktronAI and @rootxharsh were finding 0-days targeting specific vulnerabilities on OSS software.
Then we ran a full pentest-style scan on a big open-source project. The results were insane. 🧵
We tested a pre-release version of o3 and found that it frequently fabricates actions it never took, and then elaborately justifies these actions when confronted.
We were surprised, so we dug deeper 🔎🧵(1/)
https://t.co/IdBboD7NsP