We help companies deploy fleets of autonomous security agents. For threat intel and CVE updates, check out @EnclaveRadar.
United States
Joined December 2025
- Tweets279
- Following19
- Followers1.5K
- Likes666
Pinned Tweet
Node2Shell (CVE-2026-111497) is a memory bug in Brotli, the compression library bundled into Node.js, Python, system libs, Envoy and more.
Most teams don't know every place Brotli runs in their stack. It's usually a transitive dependency or an OS package, and pip-audit may not flag it yet.
Enclave's agents scan your code, cloud and servers and show you exactly where you're exposed.
Advisory + free check: app.enclave.ai/threat-feed/C…
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as “curl --compressed”) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
patchtheplanet.org/brotli
🚨 Don’t be the next Fireworks. We’ll run your pen-test and give you $1,000 in credits.
enclave.ai/startups
Enclave retweeted
If you’re a VC-backed AI company, we’ll run an initial pen-test and hardening sprint for you, so your fundraise isn’t impacted by a breach.
Reach out
Enclave retweeted
You’ve probably seen many CVSS 10.0s that end up not exploitable
Now you can get better context with technical analysis, explaining the exact exploit prerequisites.
We analyze public PoCs, how often the product is on the public internet & you get a real world exploit score.
CVSS tells you how bad a bug could be. Enclave now tells you how exploitable it is.
Every CVE in the Threat Feed with CVSS 9.8+ or exploited in the wild now gets Enclave's own agentic analysis: an exploitability score out of 10, exploit maturity, likelihood and impact, the prerequisites an attacker needs, and the sources our agents read. For any other CVE, request the analysis in one click.
Know which critical CVEs need action today, and which can wait.
app.enclave.ai/threat-feed
CVSS tells you how bad a bug could be. Enclave now tells you how exploitable it is.
Every CVE in the Threat Feed with CVSS 9.8+ or exploited in the wild now gets Enclave's own agentic analysis: an exploitability score out of 10, exploit maturity, likelihood and impact, the prerequisites an attacker needs, and the sources our agents read. For any other CVE, request the analysis in one click.
Know which critical CVEs need action today, and which can wait.
app.enclave.ai/threat-feed
An AI agent cheated its way to a perfect score on our hacking benchmark, and our verifier approved every win.
DeepSeek V4.1 Flash went 11 for 11 on vulnerable targets, but when we read the traces, five of those wins skipped the bug each challenge was built to test. On Grafana it planted its own plugin and let Grafana run it, in as little as 52 seconds, and on Jenkins it dropped the timing attack for a shorter route. Nothing in our scoring rewarded the harder path, so the agent never took it.
Then we closed every shortcut, added negative tests and a path level review of each win, and what the same model scored on the fixed benchmark: 4 of 11.
Read how we caught it and what we changed: enclave.ai/blog/how-we-caugh…
Enclave retweeted
The docs are also available through Context7!
Enclave docs are now live.
The docs walk through how Enclave maps your code and cloud, verifies which vulnerabilities an attacker can actually reach, and backs every finding with an attack path and proof. Setup, research, triage, and workflows are all covered.
Know exactly which questions Enclave can answer about your environment.
Explore: docs.enclave.ai
Enclave retweeted
We have just added docs! So many cool and useful features coming. 🚢
Stay tuned
Enclave docs are now live.
The docs walk through how Enclave maps your code and cloud, verifies which vulnerabilities an attacker can actually reach, and backs every finding with an attack path and proof. Setup, research, triage, and workflows are all covered.
Know exactly which questions Enclave can answer about your environment.
Explore: docs.enclave.ai
Enclave docs are now live.
The docs walk through how Enclave maps your code and cloud, verifies which vulnerabilities an attacker can actually reach, and backs every finding with an attack path and proof. Setup, research, triage, and workflows are all covered.
Know exactly which questions Enclave can answer about your environment.
Explore: docs.enclave.ai
Enclave retweeted
Lots of buzz (rightfully so) around this bug.
Our agentic analysis still rated exploitability 6/10 though.
One long password is all it takes, but only on musl (Alpine) sshd without PAM, with password auth on and a no-password account.
Any password over 256 characters logs into key-only accounts on Alpine's OpenSSH.
On Alpine's AWS and Azure images, that's the default alpine user. It has passwordless doas, so it's root.
No CVE yet.
*sshole is out
if you run sshd on alpine, openwrt or any musl box with password auth on: update now
official writeup: sshhole.com
Check if you're exposed:
app.enclave.ai/threat-feed/E…
Enclave retweeted
⚠️ New pre-CVE advisory, reported exploited: ENCLAVE-2026-0001
OpenSSH - sshhole - sshd accepts any long password on musl systems without PAM
On musl systems where sshd runs without PAM (Alpine's default), any password of 257–1024 bytes logs in to…
app.enclave.ai/threat-feed/E…
Enclave retweeted
Impressive work by OpenAI, as usual.
But if a model ships and almost no one can access it, did it really launch? The access gap is real.
Introducing GPT‑6 Cyber: a major advance in security research that pairs stronger capabilities with better model alignment.
The model powered the Linux kernel research we announced yesterday, and security teams at companies like Mozilla, Palo Alto Networks, Calif, and Cisco—alongside our own at OpenAI—are already putting it to work.
GPT-6 Cyber is available to select Daybreak Red customers and we are expanding access over time.
openai.com/index/introducing…
Enclave retweeted
The future of cybersecurity is fleets of autonomous and semi-autonomous agents defending your company's estate 24/7. Yes, lots of buzzwords, but I truly believe it.
Your defense will be limited only by the token and compute budget you're willing to spend.
For now, though, most companies don't have access to this tech, and they'll need help deploying it. Ideally using a model-agnostic harness/platform.
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.
Create a workspace, answer a few questions, and Enclave gets you to your first security task.
The Onboarding Assistant asks where your code lives and where it runs, then asks you to connect what's needed. It shows what's connected and what Enclave can see, then hands you off to your first task in a new chat with the prompt ready to send.
Coverage is clear before the first finding lands, and setup happens right in the chat.
Start a workspace: app.enclave.ai/
We're launching a research fellowship.
The Enclave Research Fellowship funds independent security researchers to find vulnerabilities in critical software and make the web safer.
We’re offering $1,000 every month to use for research on Enclave.
What fellows do: put Enclave's fleet of autonomous agents to work finding vulnerabilities, disclose them so they get patched, then release the research so the internet is safer for everyone.
Proven previous research is required to apply. Spaces are limited.
Apply: enclave.ai/research/fellowsh…
Why fund independent research? Critical software needs more scrutiny, and researchers need the time and resources to look.
@talhof8 shares why we started the fellowship: enclave.ai/blog/why-were-fun…
Enclave retweeted
🆕 New CVE: CVE-2026-121114 (CVSS 9.6)
Google Chrome · Remote code execution
Remote, no login needed.
Use after free in TabStrip in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a…
app.enclave.ai/threat-feed/C…
