Nice find but every vulnerability is a "xyz2shell" now?
Introducing XSS2Shell ⛓️: WordPress Core preauth XSS→RCE vulnerability affecting 43% of the internet, discovered autonomously by pwn (using open-source models), affecting all WordPress versions.
pwn.ai/blog/xss2shell
Please patch CVE-2026-64638 as soon as possible!
let me present a case of ai-induced overconfidence.
btw, if your company is doing this, call it out. it is a dumb assumption, and let me tell you why.
one of your security leads or engineers starts using claude code or codex, or builds a cool wrapper around them. it finds some bugs, of course. they run it repeatedly, burn shit ton of tokens, fix everything it finds, and eventually the scanner goes quiet.
the next thing that happens is they decide the bug bounty program is a waste of money. after all, how could some random hunter find anything their sophisticated pipeline missed? what could an external auditing firm possibly find that their agents couldn't? so they cut the program.
but if you are truly confident that your pipeline has exhausted the vulnerability space, shouldn't you be willing to increase the bounty? wouldn't that be the best way to show your c-level bros that the ai spend actually worked and wasn't wasted on some wrapper you vibecoded in a week?
or..... maybe you don't want to incentivize people to test that assumption. because how would you explain to your boss that, after burning through all those tokens, some bug bounty hunter still found a nasty vulnerability?
your cool wrapper finding bugs does not prove that no bugs remain. it only proves that the wrapper can find subset of vulnerabilities and researcher with taste will always find a way in. the entire point of a bug bounty program is to incentivize skilled researchers to find the bugs your internal tools, agents, and engineers missed.
think about it, why do openai and anthropic still run bug bounty programs that pay $100k for critical vulnerabilities? they have effectively unlimited tokens and run all kinds of crazy agent loops and automated security workflows. yet i bet they will pay that $100k, because software is vast and complex, and someone with taste will always find a bug your pipeline missed.
remember,
researcher with taste + ai(this is where your threat actors are) > good wrapper > plain claude code/codex
if your public program is drowning in slop, move it to private. invite strong researchers and pay them vip prices like github is doing. don't have this ai competence illusion which is pretty common all around.
We're partnering with @huggingface to investigate an unprecedented security incident.
Cyber-capable OpenAI models compromised Hugging Face production during a benchmark evaluation.
Sharing preliminary findings to help defenders understand emerging risks:
openai.com/index/hugging-fac…
Dipendra Shrestha retweeted
Huggingface got breached! And we will see same pattern moving further, the cloud misconfigs gonna be weakest link and will amplify the blast-radisus.. 🧵
For iniitial foothold it will be either your code, agents, or simply the saas, third-party dependencies.. as I have shown in my Metabase, Posthog blogs.
huggingface.co/blog/security…
Dipendra Shrestha retweeted
I reported a pre auth RCE in Wordpress - it can be exploited with no preconditions, patch your instances!
slcyber.io/research-center/w…
Dipendra Shrestha retweeted
doc=new DOMParser().parseFromString(`
<select>
<button>
<noscript>
<selectedcontent></selectedcontent>
</noscript>
</button>
<option>
<style></noscript><img src=x onerror=alert()></style>
</option>
</select>`,'text/html');
document.write(doc.body.innerHTML);//🔥
Dipendra Shrestha retweeted
セキュリティリサーチャー RyotaK @ryotkak の技術ブログを公開しました。
今回、Claude Code GitHub Actions の権限制御を外部の GitHub Issue 経由でバイパスし、ワークフロー権限を悪用できる脆弱性、並びにそれに付随する設定ミスを発見・報告しました。
当該の脆弱性は v1.0.94 で修正済みですが、設定ミスについては各リポジトリにて対応が必要であるため、当該製品を利用されている場合は設定の見直しと実行ログの確認を推奨します。
flatt.tech/research/posts/po…
Dipendra Shrestha retweeted
Posting a mini XSS challenge! Goal is to pop an alert. I believe this trick is not well known. Intended solution is chrome only. Thanks to @kevin_mizu for beta testing! Don't post solutions in the thread; DM only!
xss.hashkitten.io/xss1.html
Dipendra Shrestha retweeted
That's my chain — a full chain w/ logic bugs only! No memory corruption, no AI, and of course no collisions at all 😉
Confirmed! Orange Tsai (@orange_8361) of DEVCORE Research Team (@d3vc0r3) chained 4 logic bugs to achieve a sandbox escape on Microsoft Edge, earning $175,000 and 17.5 Master of Pwn points. Full win! #Pwn2Own #P2OBerlin
Dipendra Shrestha retweeted
I started playing CTFs in 2022, and LLMs definitely changed the **competitive** CTF scene a lot, especially since mid-2025. I also started using LLMs in late 2025. Yes, those models did one-shot many challenges, but what's the fun of slopping them? I learned absolutely nothing 🥲
Dipendra Shrestha retweeted
i built an entire x86 CPU emulator in CSS (no javascript)
you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS
I’ve been digging into HTTP Trailers and found some new smuggling techniques:
sebsrt.xyz/blog/trailing-dan…
Dipendra Shrestha retweeted
Chrome implements referrerpolicy on <input type="image">, despite it not being in the HTML spec. Like on the in-spec elements, it takes precedence over the document policy for that request and can be abused to leak the page URL via the Referer header.
storage.googleapis.com/nowas…
Dipendra Shrestha retweeted
Cross-Site ETag Length Leak
blog.arkark.dev/2025/12/26/e…
I just posted the author writeup for impossible-leak in SECCON CTF 14 Quals. As far as I know, this is a new XS-Leak technique! The ETag header can become a side channel :)




























