inzo Profile
inzo

@inzo____

Followers
3K
Following
1K
Media
36
Statuses
199

always hunting for the unseen;

Joined November 2022
Don't wanna be here? Send us removal request.
@inzo____
inzo
7 months
Happy to share my first article with @zhero___, which is also my first CVE (CVE-2025-29927) on the largest JS framework: Next.js. A critical vulnerability that impacts a wide range of sensitive sectors across the internet.
@zhero___
zhero;
7 months
the research paper is out: Next.js and the corrupt middleware: the authorizing artifact result of a collaboration with @inzo____ that led to CVE-2025-29927 (9.1-critical) https://t.co/GZkbnr6o9H enjoy the read!
8
15
214
@zhero___
zhero;
3 months
frameworks, frameworks with @inzo____
2
5
159
@inzo____
inzo
3 months
I really enjoyed reading the latest research paper by @albinowax Big kudos to everyone who contributed to this research Super inspiring https://t.co/VzGwkcMjoH
Tweet card summary image
portswigger.net
Abstract Upstream HTTP/1.1 is inherently insecure and regularly exposes millions of websites to hostile takeover. Six years of attempted mitigations have hidden the issue, but failed to fix it. This p
@albinowax
James Kettle
3 months
The whitepaper is live! Learn how to win the HTTP desync endgame... and why HTTP/1.1 needs to die:
2
1
54
@zhero___
zhero;
4 months
new discovery: cache poisoning on next.js - CVE-2025-49826 indefinite caching of a 204 response, rendering the affected pages inaccessible affected versions: >15.0.4 and <15.2.0 there will be no research paper for this one
@inzo____
inzo
4 months
back to work with @zhero___ and a new vulnerability on @nextjs that led to CVE-2025-49826 both routers are impacted: app router: framework's cache is directly impacted on ISR pages, regardless of the presence of a CDN pages router: SSR pages only + requires a misconfigured CDN
14
84
483
@inzo____
inzo
4 months
back to work with @zhero___ and a new vulnerability on @nextjs that led to CVE-2025-49826 both routers are impacted: app router: framework's cache is directly impacted on ISR pages, regardless of the presence of a CDN pages router: SSR pages only + requires a misconfigured CDN
4
20
220
@zhero___
zhero;
4 months
Bug bounty, feedback, strategy, and alchemy frequently asked for advice, roadmaps, and more, I finally took the time, after 2–3 years of bug bounty, to write down my vision, thoughts and perspective on the subject non-technical, no research this time! https://t.co/QirdoupcnU
22
83
417
@inzo____
inzo
5 months
@zhero___ In the meantime, @zhero___ published a very interesting piece of research https://t.co/cLGI3obrss
@zhero___
zhero;
6 months
publication of my latest modest paper; Eclipse on Next.js: Conditioned exploitation of an intended race-condition - (CVE-2025-32421) enabling a partial bypass of my previous vulnerability, CVE-2024-46982 by chaining a race-condition to a cache-poisoning https://t.co/NV8IYWvkil
0
0
16
@inzo____
inzo
5 months
After a few days off, I'm back to work with @zhero___, and we've just reported a new high-severity vulnerability in a major open-source framework.
10
3
127
@inzo____
inzo
6 months
The real key is to focus on maximizing your bug hunting income, making smart investments, and ultimately transitioning to full-time zero-day research once your investments cover all your living expenses.
@bxmbn
🇪🇨🍫
6 months
The key is to maximize your bug hunting income, invest wisely, and gradually stop hunting as your investments fully cover your expenses. 🤓☝️
3
2
97
@vercel_dev
Vercel Developers
6 months
Vercel customers are protected from two high-severity vulnerabilities (CVE-2025-43864 and CVE-2025-43865) in Remix and React Router. Read our advisory to understand impact and next steps. https://t.co/jmPW2qHxWA
Tweet card summary image
vercel.com
Security researchers reviewing the Remix web framework have discovered two high-severity vulnerabilities in React Router. Vercel proactively deployed mitigation to the Vercel Firewall and Vercel...
1
8
61
@zhero___
zhero;
6 months
another research effort with @inzo____ led to the discovery of two new vulnerabilities in React Router (14M+ downloads/week), resulting in: - CVE-2025-43865 (High-8.2) - CVE-2025-43864 (High-7.5)
26
67
623
@zhero___
zhero;
7 months
back to work, a sleepless night and 2 open-source vulnerability reports submitted; back on track with @inzo____
6
2
175
@inzo____
inzo
7 months
- d o p a m i n e, more d o p a m i n e Finish the month of March with some nice bounties with @zhero___! Who can say better?
@zhero___
zhero;
1 year
`re you sure you're okay? - d o p a m i n e, more d o p a m i n e
9
3
164
@zhero___
zhero;
7 months
new paper on a vulnerability discovered in React Router, resulting from a collaboration with @inzo____ that led to CVE-2025-31137; React Router and the Remix'ed path https://t.co/LMiqASwZnf good reading
32
149
780
@zhero___
zhero;
7 months
> valid reports frantically closed by the same analyst who doesn't understand the vuln (nor tries/ask) > mediation disabled for these reports(?) > reports resent hoping to find a different analyst > same analyst, reports closed listen, here, what I don't understand doesn't exist
9
13
184
@zhero___
zhero;
7 months
new open-source software vulnerability report sent with @inzo____ let's see;
13
4
257
@_JohnHammond
John Hammond
7 months
The 9.1 CVSS CVE-2025-29927 authentication bypass vulnerability in Next.js middleware -- covered in a rambling video and teeny tiny demo showcase, ✨ V I B E C O D I N G✨ a vulnerable proof-of-concept app. https://t.co/DUUxBFDAJc
7
59
334
@zhero___
zhero;
7 months
the research paper is out: Next.js and the corrupt middleware: the authorizing artifact result of a collaboration with @inzo____ that led to CVE-2025-29927 (9.1-critical) https://t.co/GZkbnr6o9H enjoy the read!
73
450
2K
@nextjs
Next.js
7 months
Next.js 15.2.3 includes a security vulnerability patch. We recommend updating to 15.2.3 or backported patches. If you cannot update, we have included guidance for how to protect your application. Apps on Vercel, Netlify, and Cloudflare are not affected. https://t.co/9rLVZf1HCt
Tweet card summary image
vercel.com
Last week, we published CVE-2025-29927 and patched a critical severity vulnerability in Next.js. Here’s our post-incident analysis and next steps.
45
261
2K