I'm in my churn era.
Charging me too much? I'll slop up a replacement.
Bad MCP server? I'm sure Claude can make a better one.
Slow to respond? Claude isn't.
Missing important features? You know what's a prompt away...
Seriously, if you aren't keeping up with the needs of your fastest moving customers, you are going to be replaced.
if you’re working for a company in cybersecurity, you should be evaluating your options to abstract your companies services from the internet
what i mean is: why allow an unauthenticated anonymous agent of an attacker to interact with your systems?
consider your architectural levers now, you’re going to need them
Jede Maschine, jeder Roboter, jede Software, die einen Menschen produktiver macht, ist für ein Land mit unserer Alterspyramide keine Bedrohung. Sie ist die Bedingung dafür, dass es weitergeht.
I've led vulnerability management for some very large companies. I've been in the trusted embargo 0day info sharing rooms.
I think it would be negligent at this point to assume that they will be the norm moving forward.
We can't expect to get a nice coordinated vuln announcement and patch handed to us in private with weeks to handle it.
We need layers of defense so 0days in internet facing devices won't be catastrophic. We need machine speed detections and response.
And of course we need to figure out the new norm of how we handle 0days in hours not days. This will take agents and harnesses you might not have yet.
A lot of this has been true for a while, but you could get away with handling in fire drill mode when happened and put off the actual engineering.
As people are saying, the interest rates on security tech debt just skyrocketed.
@Kostastsale Wow, incredible. Can you reverse engineer elasticsearch next and put the source code online? I heard someone already did this with Blender too
‼️ALERT - Two new unpatched CVSS 9.0 RCE flaws in #Linux's KSMBD SMB server were disclosed on public kernel mailing lists before fixes were ready.
One can be triggered WITHOUT authentication.
Neither has a mainline kernel fix.
Details here ↓ https://t.co/0MIHpvkPIQ
🚨 PHP2Shell detection is now available in Burp Suite Professional & Burp Suite DAST.
Most of the web is powered by PHP, which means most of the web is vulnerable to these critical unauthenticated remote code execution flaws (CVE-2026-109618 / 109619). You can already detect it in Burp Suite using:
🟧 ActiveScan++ v2.0.13 (https://t.co/fkhECQ6wtD)
🟧 Bambda scan checks (https://t.co/PxPcj5uDYX)
🟧 BChecks (https://t.co/i8c8WiDnvb)
Start scanning for the vulnerability now → https://t.co/fkhECQ6wtD
We replicated today's PHP session exploit. Disabling sessions does not prevent it.
We took our servers offline until PHP releases the patch. Every host should do the same.
Especially WPorg. The forced autoupdate backdoor reaches every site and grows more severe every day.
If their systems get compromised, any major plugin can be wiped off the face of Earth within 3 hours.
Teamwork makes the dream work.
The team and I
@J4ck3LSyN@Archknight23
🚨 Heads-up for anyone running PHP: two critical RCE bugs, patch drops tomorrow.
The PHP project has confirmed an emergency security release for two critical remote code execution vulnerabilities: CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2.
📅 Patch lands Wednesday, Oct 21 at 14:00 UTC (9:00 AM Central). PHP has reserved the right to ship it earlier if details leak or exploitation shows up.
PHP runs about 75% of the web, including WordPress, Drupal, Joomla, Laravel, Magento, and countless custom apps. If you operate a PHP server, this is your weekend-ruiner unless you act.
Here's the part the big threat-intel shops aren't shouting about:
No official technical details are public yet. But based on my own source-code analysis of php-src, my best assessment (moderate confidence, NOT officially confirmed) is that the vulnerable path is PHP's session.upload_progress / multipart form-data (rfc1867) handling:
🔹 Present since PHP 5.4
🔹 Enabled by default (the compiled-in default is On; the sample php.ini ships it commented out, so stock installs have it live)
🔹 Processes uploaded request data before any of your application code runs, so it's reachable pre-authentication on a default config
That lines up exactly with the public breadcrumbs: "affects default installs," "every version since 5.x," "fires before user code." Treat it as a working hypothesis, not gospel. The official advisory supersedes all of this when it lands.
✅ What to do right now:
1. Inventory your PHP. Know every host and version (php -v). Anything on PHP 7.x or older won't get a fix, so plan to upgrade.
2. Apply the stopgap (best-intel, low-risk, reversible). In php.ini / .user.ini / .htaccess:
session.upload_progress.enabled = Off
Reload PHP-FPM or your web server. My analysis says this closes one of the two likely paths.
3. Clamp multipart uploads at the edge. The second likely path lives in the multipart parser itself, which runs for any multipart/form-data POST regardless of the setting above. If you've got a WAF or reverse proxy, tighten inspection or rate-limit multipart POSTs to endpoints that don't need uploads. This is the same network-layer mitigation the enterprise vendors are quietly deploying for their paying customers.
4. Patch the second it drops. Current stable: 8.5.11 / 8.4.26 / 8.3.35 / 8.2.34. If your hosting is managed, confirm your provider's timeline today.
Why I'm posting this for free:
A pre-patch mitigation shouldn't be a subscription perk. I'm a one man shop, and the orgs most likely to get burned in the gap between leak and patch are the small teams without an enterprise threat intel contract. The steps above cost nothing. Spend tonight reducing risk, not tomorrow doing incident response.
I'll follow up once the official advisory publishes and confirm whether my root cause read was right.
Stay patched. 🔒
#PHP #CyberSecurity #InfoSec #RCE #CVE #WordPress #Laravel #ThreatIntel #VulnerabilityManagement #AppSec
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.
PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
@ZackKorman as with all things in cyber, good prevention > good detection > good response.
you still need all three, because prevention is never perfect.
For the cost of 8 years of $200 Claude subs, you can force your team to use shitty quantized versions of DeepSeek v4 Flash running at 30tps. Incredible deal!
We’re expanding our Cyber Verification Program to give security professionals broader access to our most capable models.
Through this program, verified security professionals can access Claude Mythos 5.1, Opus 5.5, and Sonnet 5.5 with safeguards designed for defensive work.
We’re also opening up new tiers to allow for authorized offensive work, like penetration testing and red-teaming.
https://t.co/blaJtvxhJh
Highest ROI for hiring a security engineer today than ever before.
The tools are getting GOOD, like really good. You can find and fix bugs. You WILL find bugs, but you have to be looking.
Either invest in seceng+tooling now, or spend ++money responding to incidents.
@markusdd5 In my experience astra has struggled massively with “first-time-right” compared to Claude
Yes, the code works, but in review I find lots of security flaws and non-adherence to internal coding guidelines.
~30% of the PRs by Astra still need fixing by Claude, but might just be me