Marc Wickenden (@marcwickenden) header
Marc Wickenden (@marcwickenden) profile picture

Cloud AppSec Bloke. Kubernetes, Go, Python, cycling, YAML engineering. Builder and breaker @4ARMED. It was like that when I found it.

Visual Code
Joined February 2011
Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)Photo by Marc Wickenden (@marcwickenden)
Marc Wickenden retweeted
This week has been quite a shitshow already, and there are still 2 days to go Here’s a quick recap of the security mess we’ve seen in just the last few days: 1. PHP Core RCE (CVSS 9.2) Two critical vulnerabilities (CVE-2026-109618/109619) allowing unauthenticated RCE. A huge number of PHP installations potentially affected, and there are already reports of reliable exploitation against patched versions. Great… Useful links: Official PHP advisory and patches: php.net/archive/2026.php#202… Practical hardening and mitigation guide by Vincent Schmalbach. nginx/Apache configurations, PHP settings, patch verification and compromise checks: vincentschmalbach.com/cve-20… Huntress analysis. What to monitor, suspicious child processes, webshells and post-exploitation activity: huntress.com/blog/php2shell-… Wiz technical deep dive. Exploit mechanics, memory disclosure, affected applications and the role of AI: wiz.io/blog/php2shell-php-rc… Corelight’s open-source Zeek and Suricata detection rules: github.com/corelight/php2she… 2. GitLab RCE (CVSS 10.0) CVE-2026-110264. An integer overflow in the regex compiler leading to unauthenticated RCE. Apparently affects around 12 years(!) of GitLab releases. docs.gitlab.com/releases/pat… 3. Node.js / Brotli RCE CVE-2026-111497. An out-of-bounds write in the Brotli decoder that can lead to RCE when processing malicious compressed data. Node.js 22, 24 and 26 affected. nodejs.org/en/blog/vulnerabi… 4. DNS-over-QUIC DoS CVE-2026-97206. A use-after-free in Unbound’s DNS-over-QUIC implementation. Remote attackers can crash affected multi-threaded DNS resolvers. nlnetlabs.nl/projects/unboun… 5. eMudhra CA disaster And then there’s this absolute PKI clusterfuck. Eight intermediate CA private keys turned out to be ridiculously easy to reconstruct. Browser vendors have started blocking the affected CAs, but outdated clients and applications with their own trust stores could keep accepting certificates from them. Cleaning up this mess is a lot harder than just patching a server. Google’s analysis and response: blog.google/security/protect… Mozilla’s public incident investigation, including the technical findings, timeline and eMudhra’s explanations: bugzilla.mozilla.org/show_bu… — And I can’t help wondering how much of this sudden wave of discoveries has to do with the latest AI models getting better at code review and vulnerability research. We now have models that can dig through massive codebases and potentially find bugs that have been sitting there for years. I’m not saying these particular vulnerabilities were discovered using AI. I haven’t seen evidence for that. But I do wonder whether we’re starting to see some of the effects. The eMudhra case is obviously a different story. That’s a spectacular failure of key management and quality control. Anyway, quite a week. And it’s only Thursday…
🤖 Made with AI
42
180
16
634
74,464
Marc Wickenden retweeted
China published the most uncomfortable paper on vibe coding. ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds. The findings are brutal. The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning. They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself. Two major predictors emerged. Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds. But that wasn't even the main takeaway. Computer science achievement was a massive, dominant predictor of success. Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed. In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone. Why? Because vibe coding isn't about writing code. It’s about debugging logic. When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works. They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe. You can prompt your way past syntax. You cannot prompt your way past a fundamental lack of engineering intuition. The hype told us that learning to code is dead because language is all you need. The data just proved the opposite. To truly master the vibe, you still need to understand how the machine thinks.
312
1,316
385
7,149
806,993
Marc Wickenden retweeted
Http11Probe: An open testing platform that probes HTTP/1.1 servers against RFC 9110/9112 requirements, smuggling vectors, and malformed input handling. mda2av.github.io/Http11Probe…
5
6
1,185
Marc Wickenden retweeted
New: I'm sharing the @trailofbits Claude Code defaults. This is how we setup, configure, and use claude code: github.com/trailofbits/claud…
44
153
11
1,110
92,164
Marc Wickenden retweeted
Literally every old school hacker out there dreamed of achieving a find like this: msrc.microsoft.com/update-gu…
6
41
3
343
41,255
A day out of the office for a change at @ConDaysEU. Looking forward to this. Tip if anyone’s waiting for coffee, there’s a second one in the vendor area with less queue #urwelcome #condayseu
51
Marc Wickenden retweeted
Evaluating and mitigating the growing risk of LLM-discovered 0-days Best lunch break read I had in a while So, the 500 critical security vulnerabilities is what OffSec missed all these years red.anthropic.com/2026/zero-…
7
72
5
380
36,969
Marc Wickenden retweeted
More skill issues: “npx skills add” copies everything, including symlinks! Malicious skills can then exfiltrate any file on your machine, including ~/.ssh/id_rsa. Opus 4.5 normally checks files to block data exfil, but using a symlink bypasses that. More details below.
13
26
7
148
27,626
I’ve got $5k of credits on @digitalocean and honestly I think I would rather spend money and use anything else at this point. DO has a great “dev” experience but ye gods it’s a bloody nightmare to actually run a modest prod platform on it. And IAM is a clearly a dirty word #rant
1
1
165
Spaces access keys can’t be scoped to a bucket, let alone a subresource. Requests to raise our droplet limit above 10 have not been actioned. Have you ever tried to run _anything_ on only 10 nodes when the max memory you can choose is 8GB?
1
116
I do love DO but the more you use it the more you realise what you pay for when you go to the big three.
1
100
Toggle user privacy: Backend: Add protobuf spec, compile, add handler, add GraphQL mutation spec, compile, define handler. 5 minutes. Frontend: Add toggle switch that uses mutation on change. 1 hour and counting…. I hate doing front end. 😂
1
129
Marc Wickenden retweeted
#linux users right now 🐧
288
4,085
475
24,316
1,589,474
All of the Tifosi if Fred signs both Lewis Hamilton and Adrian Newey in one year
290
2,936
235
37,977
1,509,982
Definitely don't have #KubeCon FOMO. Nope. Not one bit....
2
161