
If you have dependencies, you should be watching their commit logs. Don't wait for the CVE.

SecEng @tines_hq Previously: SWE @Datadog CEO/ Founder of @graplsec SecEng @Dropbox SWE @Rapid7

If you have dependencies, you should be watching their commit logs. Don't wait for the CVE.

Can we make C illegal yet? Can't believe you can deploy software like nginx to a fedramp environment but you can't use chacha lol


People are just larping as security experts. Containers can definitely be a security boundary. Whether they are or not depends on use case and threat model. They certainly aren't/shouldn't be a boundary for cloud providers, which is probably the use case most people think about.
I keep seeing posts that containers aren't security boundaries. But I have mapped read-only volumes, SELinux, isolated networks? Certainly it's to SOME degree a boundary? What am I missing?

Patches are now exploit tutorials. csoonline.com/article/424959…


True, but regardless of exploitability, the meme potential after the PHP2Shell scoff-fest is off the charts though

Have a functional exploit POC for CVE-2026-114938 aka Java4Shell. This is not a generic exploit and will need to be application specific, you need a CPU with AVX-512 VBMI support, vulnerable JDK Version, and the app needs to use Base64, note that tomcats basic auth and java-jwt provide pre-auth exploitable path. This time it was GLM5.3 was running my agents instead of Claude Code

java4shell exists because java is too slow to be memory safe

At Tines 3B, we spin up millions of gVisor sandboxes a day. Each runs a 3B step from an image built from code a user or agent has written. An interesting problem with this setup is getting that image running quickly when the sandbox starts fresh every time.

Nice argument, but I’ve already released a 12M-line lean formalization that you are the soyjack and I am the chad.


DBSC, DPoP, end to end encryption. Happy @dinodaizovi ?

New 3B crypto implementation released today. Multiple services can be compromised all at once, including our edge API service, and secrets still can't be revealed to an attacker.

DBSC is globally deployed to 3B. If you use Chrome to log into 3B you'll automatically benefit from this change.

Rust compiler: "What if this pointer outlives the data?" C compiler: "What if it doesn’t? Why are you always so negative?"