## Updated at UTC 2026-11-16T18:37:21.653877

Access data as JSON

CVE CVSS EPSS Posts Repos Nuclei Updated Description
CVE-2026-111559 None 0.00% 1 1 2026-11-16T18:30:38 Batflat CMS does not sanitize data passed to the /contact endpoint. A remote una
CVE-2026-91115 8.8 0.00% 2 0 2026-11-16T17:17:37.480000 Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Fro
CVE-2026-113630 7.8 0.00% 2 0 2026-11-16T17:17:29.080000 Command injection in the documentserver-flush-cache.sh maintenance helper in ONL
CVE-2026-109618 9.8 100.00% 2 100 2026-11-16T16:54:58.603000 PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context an
CVE-2026-129947 8.0 0.00% 2 0 2026-11-16T15:31:07 Contentlayer @contentlayer/core through 0.3.4 contains a code injection vulnerab
CVE-2026-129948 8.8 0.00% 2 0 2026-11-16T15:31:06 Contentlayer @contentlayer/source-files through 0.3.4 contains a code injection
CVE-2026-129952 9.8 0.00% 2 0 2026-11-16T15:31:06 NodePress through 8.5.1 contains an authentication bypass vulnerability that all
CVE-2026-129955 9.8 0.00% 2 0 2026-11-16T15:31:06 NodePress through 8.5.1 contains an authentication bypass vulnerability that all
CVE-2026-129956 7.8 0.00% 2 0 2026-11-16T15:31:00 Sandboxie-Plus before 1.18.6 contains a local privilege escalation vulnerability
CVE-2026-129941 9.8 0.00% 4 0 2026-11-16T15:30:57 Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an authentication bypas
CVE-2026-19732 9.9 0.00% 2 0 2026-11-16T15:30:44 An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERI
CVE-2026-77033 9.9 0.00% 2 0 2026-11-16T15:30:44 An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERI
CVE-2026-93664 10.0 0.00% 2 0 2026-11-16T15:17:34.640000 A Deserialization of Untrusted Data vulnerability affecting Station Launcher App
CVE-2026-129880 7.7 0.00% 2 0 2026-11-16T15:17:27.043000 DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vuln
CVE-2026-129874 8.8 0.00% 2 0 2026-11-16T15:17:26.183000 REBUILD 3.5.0 through 4.5.4 contains a privilege escalation vulnerability that a
CVE-2026-124021 8.1 0.67% 2 1 2026-11-16T14:17:05.877000 Control Web Panel (CWP) before webpanel_version 1.30.6 contains an authorization
CVE-2026-124020 8.1 0.65% 2 2 2026-11-16T14:17:05.740000 Control Web Panel (CWP) before webpanel_version 1.30.6 contains a host header in
CVE-2026-129552 9.8 0.00% 2 0 2026-11-16T12:31:50 Tensei through 0.11.5 contains an authentication bypass vulnerability in @tensei
CVE-2026-129550 9.1 0.00% 4 0 2026-11-16T12:31:49 Tensei through 0.11.5 contains a privilege escalation vulnerability in @tensei/a
CVE-2026-99288 0 0.16% 4 1 2026-11-16T01:17:20.233000 In the Linux kernel, the following vulnerability has been resolved: inet: rejec
CVE-2026-129349 None 0.60% 2 1 2026-11-15T12:31:29 When authentication caching is enabled on DefaultLdapRealm, after a user logs in
CVE-2026-119618 8.1 1.58% 1 15 2026-11-15T03:30:44 Concurrent Execution using Shared Resource with Improper Synchronization vulnera
CVE-2026-114713 8.6 0.51% 1 3 2026-11-13T21:31:48 The labeled-response module in UnrealIRCd 6.0.0 before 6.2.7.1 does not escape t
CVE-2026-118383 9.0 0.74% 1 1 2026-11-13T15:56:12.173000 A use-after-free in the replication component of MongoDB Server can occur when a
CVE-2026-6460 8.8 0.59% 1 10 2026-11-13T05:18:53.517000 Type confusion in PostgreSQL allows an object creator to execute arbitrary code
CVE-2026-120868 0 0.29% 4 1 2026-11-13T00:20:09.977000 Memory overflow in Packet Processing can lead to unpredictable or erroneous beha
CVE-2026-98432 9.8 0.78% 1 88 2026-11-12T18:31:14 In the Linux kernel, the following vulnerability has been resolved: ipv4: free
CVE-2026-76964 10.0 0.43% 1 1 2026-11-11T11:17:20.903000 SAP NetWeaver Application Server ABAP does not sufficiently validate certain net
CVE-2026-89126 10.0 0.43% 1 1 2026-11-11T05:19:55.120000 SAP Web Dispatcher does not sufficiently validate certain network input processe
CVE-2026-105616 5.7 0.19% 1 0 2026-10-28T18:32:11 PostgreSQL restricts acces to the salt and shift via the `SHOW` command for user
CVE-2026-65339 5.0 0.15% 3 0 2026-10-26T21:35:42 A logic issue was addressed with improved checks. This issue is fixed in iOS 26.
CVE-2026-42271 8.8 91.44% 2 2 2026-10-26T20:10:00.160000 LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) fo
CVE-2025-55182 10.0 99.73% 1 100 2026-10-18T17:10:00.110000 A pre-authentication remote code execution vulnerability exists in React Server
CVE-2026-93690 7.5 0.45% 1 0 2026-09-22T20:25:55.870000 uri-js through 4.4.1 contains a denial of service vulnerability in the removeDot
CVE-2026-86520 7.5 0.41% 1 0 2026-09-18T18:32:03 Bransys ELD is shipped with hardcoded MQTT credentials, which will grant read ac
CVE-2026-48710 6.5 70.29% 2 5 2026-08-28T18:31:00 ### Summary In affected versions, the HTTP `Host` request header was not validat
CVE-2026-77806 9.8 4.48% 1 1 2026-08-21T15:32:18 SPIP before 4.4.21 allows unauthenticated remote attackers to execute arbitrary
CVE-2026-73080 9.3 0.53% 2 0 2026-08-11T15:58:24 ### Impact `VolumeServer.FetchAndWriteNeedle` fetches a caller-supplied remote e
CVE-2026-23903 5.3 0.40% 2 0 2026-02-11T19:48:44 ### Impact **Authentication Bypass:** A vulnerability exists in Apache Shiro th
CVE-2017-9841 9.8 100.00% 1 17 2025-10-22T17:32:08 Util/PHP/eval-stdin.php in PHPUnit starting with 4.8.19 and before 4.8.28, as we
CVE-2024-50340 7.3 61.83% 1 1 2024-11-06T23:39:52 ### Description When the `register_argc_argv` php directive is set to `on` , an
CVE-2026-84384 0 0.52% 1 0 N/A
CVE-2026-118268 0 0.00% 2 0 N/A
CVE-2026-118269 0 0.00% 2 0 N/A
CVE-2026-109619 0 100.00% 2 100 N/A
CVE-2026-110710 0 0.00% 2 0 N/A

CVE-2026-111559(CVSS UNKNOWN)

EPSS: 0.00%

updated 2026-11-16T18:30:38

1 posts

Batflat CMS does not sanitize data passed to the /contact endpoint. A remote unauthenticated attacker can send a POST request with a crafted message, causing arbitrary PHP code execution with www-data user privileges. The project is no longer maintained and the issue has not been fixed.

1 repos

https://github.com/Tymbark7372/CVE-2026-111559

offseq@infosec.exchange at 2026-11-16T13:00:38.000Z ##

Batflat CMS (v1.2.0 – 1.3.6) hit by CRITICAL RCE via /contact (CVE-2026-111559). Unauthenticated remote attackers can execute PHP as www-data. No fix — migrate or isolate ASAP. radar.offseq.com/threat/cve-20 #OffSeq #CVE2026111559 #infosec #vulnerability

##

CVE-2026-91115
(8.8 HIGH)

EPSS: 0.00%

updated 2026-11-16T17:17:37.480000

2 posts

Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. From 6.0.0 until 6.2.13, the writer option of i18nTextCollectorTask is passed to the dependency injector without validating that it names an allowed writer implementation. A crafted dev task URL can therefore instantiate arbitrary objects with attacker-controlled constructor arguments and execute code on the server. An ad

thehackerwire@mastodon.social at 2026-11-16T17:49:30.000Z ##

🟠 CVE-2026-91115 - High (8.8)

Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. From 6.0.0 until 6.2.13, the writer option of i18nTextCollectorTask is passed to the dependency injector without validating that it names an allowed writer implementation...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T17:49:30.000Z ##

🟠 CVE-2026-91115 - High (8.8)

Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. From 6.0.0 until 6.2.13, the writer option of i18nTextCollectorTask is passed to the dependency injector without validating that it names an allowed writer implementation...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-113630
(7.8 HIGH)

EPSS: 0.00%

updated 2026-11-16T17:17:29.080000

2 posts

Command injection in the documentserver-flush-cache.sh maintenance helper in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows a local attacker with command execution as the ds user to execute arbitrary commands as root via a crafted --hash argument that is interpolated unvalidated into a GNU sed expression, where the sed e flag runs attacker-co

thehackerwire@mastodon.social at 2026-11-16T18:05:07.000Z ##

🟠 CVE-2026-113630 - High (7.8)

Command injection in the documentserver-flush-cache.sh maintenance helper in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows a local attacker with command execution as the ds user to execute a...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T18:05:07.000Z ##

🟠 CVE-2026-113630 - High (7.8)

Command injection in the documentserver-flush-cache.sh maintenance helper in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows a local attacker with command execution as the ds user to execute a...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-109618
(9.8 CRITICAL)

EPSS: 100.00%

updated 2026-11-16T16:54:58.603000

2 posts

PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and le

100 repos

https://github.com/Liam-G/php2shell-audit

https://github.com/waksboy/fixed-fpm-cve-2026-109618-and-109619-images

https://github.com/HackSpeak/CVE-2026-109618

https://github.com/revonnet/php-fix

https://github.com/GlobalsecureAcademy/php2shell-scanner-CVE-2026-109618-CVE-2026-109619

https://github.com/akaihigurashi/php2scan

https://github.com/getastra/php2shell-triage

https://github.com/yetDevs/php2shell-triage

https://github.com/cyberkiddle/CVE-2026-109618

https://github.com/hypnguyen1209/php2shell

https://github.com/1amrahul/php2shell-cve-2026-109618-cve-2026-109619

https://github.com/mefulton/CVE-2026-109618-analysis

https://github.com/alvarodh5/php2shell

https://github.com/ersinkoc/php-fix

https://github.com/umair-aziz025/PHP2Shell

https://github.com/JoasASantos/php2shell-scanner

https://github.com/david-alvarez-rosa/php-rce

https://github.com/syrex1013/php2shell

https://github.com/brentmartinmiller/php2shell-check

https://github.com/djad04/php2shell-deep-dive

https://github.com/RuanSerraAzul/CVE-2026-109618-POC

https://github.com/agrresore/php2shell

https://github.com/Stonlifer/php2shell

https://github.com/eness/php2shell-CVE-2026-109618-CVE-2026-109619-PoC

https://github.com/exception0x876/php74-el7-patched

https://github.com/gumerzzzindo/php2shell-CVE-2026-109618-109619

https://github.com/Nayrae/CVE-2026-109618

https://github.com/assetnote/php2shell-scanner

https://github.com/godylockz/CVE-2026-109618-109619

https://github.com/AmpedWasTaken/PHP2Shell-CVE-2026-109618-CVE-2026-109619

https://github.com/cloudducoeur/ansible-playbook-CVE-2026-109618

https://github.com/Blue-B/php2shell-guard

https://github.com/bagusindrayana/php-vuln-scan

https://github.com/HOSTED-POWER/php_uploadprogress_guard

https://github.com/0xrsydn/php2shell-scan

https://github.com/junaire/CVE-2026-109618-exploit

https://github.com/deconstruction/EOLphp-php2shell-patches

https://github.com/mirrored-projects/PHP74-Windows-CVE2026

https://github.com/ivanscm/php80-cve-2026-109618

https://github.com/syhunt/php2shell-protection

https://github.com/bahartanir/php2shell

https://github.com/sahmsec/CVE-2026-109618-PHP2SHELL

https://github.com/aarsaputra/php2shell

https://github.com/slabbdev/php2shell-cve-2026-109618-109619

https://github.com/enactive-systems/CVE-2026-109618-poc

https://github.com/Anton-Barinov/php2shell-patches

https://github.com/mpyw/php-eol-CVE-2026-109618-109619

https://github.com/open0x01/php2shell

https://github.com/Bhavye-Malhotra/php2shell-2026

https://github.com/PasqualePillitteri/php2shell-hardening

https://github.com/Is4yev/php2shell-poc

https://github.com/lzz0403/CVE-2026-109618-PHP2Shell-poc

https://github.com/cozybear-dev/cve-2026-109618

https://github.com/dinosn/php-cve-2026-10961x-lab-poc

https://github.com/mnk-works/php2shell-verify

https://github.com/zr0n/php2shell

https://github.com/VABISMO/php2shell-nginx-fpm-full-rce

https://github.com/covertswarmlabs/PHP2Shell-Check

https://github.com/WoYinDao/CVE-2026-109618-CVSS-9.2-Critical

https://github.com/Ethen1212/php2shell-CVE-2026-109618

https://github.com/xaviware/go-php2shell-scanner-CVE-2026-109618-CVE-2026-109619

https://github.com/zenzue/CVE-2026-109618_19

https://github.com/Galeax/php2shell-scanner

https://github.com/pax-k/Php2Shell-POC

https://github.com/Felix3322/PHP-uniDoS

https://github.com/Galeax/PHP2Shell-Mitigations

https://github.com/zhqagp/php-7.2

https://github.com/mehmet-emir-eroglu/PHP2SHELL

https://github.com/pentestershell/php2shellbt

https://github.com/break-the-build/php-multipart-waf-signals

https://github.com/CyberRoute/php2shell-scanner

https://github.com/ericmann/php2shell-ioc

https://github.com/kuwoo/php2shell-Lab

https://github.com/softjapan/php74-cve-patched

https://github.com/CompleteTech-Security/php2shell-check

https://github.com/devploit/php2shell

https://github.com/corelight/php2shell-detect

https://github.com/ikow/php2shell-poc

https://github.com/ginoa79/php56-php2shell-backport

https://github.com/Niek/php7

https://github.com/Noshadi-sec/cve-2026-109618-109619-poc

https://github.com/MakFly/php2shell-check

https://github.com/Qsnh/php2shell-fixed

https://github.com/mikensec/php2shell-lab

https://github.com/tani2shell/php2shell-lab

https://github.com/yashasrnair/php2shell

https://github.com/Bulletdev/php2shell-poc

https://github.com/EngOREOO/php2shell-CVE-2026-109618-CVE-2026-109619-PoC

https://github.com/xuehuolll/php2shell-CVE-2026-109618-109619

https://github.com/alham-rizvi/php2shell-scanner

https://github.com/aancw/php2shell-scanner

https://github.com/Chr1s-T/php2shell-cve-2026-109618

https://github.com/SamJUK/php2shell-check-cve-2026-109618

https://github.com/meuhland/php-legacy-windows-builds

https://github.com/0x4148/CVE-2026-109618-php2shell-lab

https://github.com/toxy4ny/php2shell-checker

https://github.com/murrez/php2shell

https://github.com/vperetti/php-cve-2026-109618-109619-backports

https://github.com/pruiz/php-CVE-2026-109618

https://github.com/JoasASantos/php2shell-exploit

greenido.dev@greenido.dev at 2026-11-16T13:55:00.000Z ##

When AI Starts Finding Zero-Days, Breaking Sandboxes, and Hacking Infrastructure

There is a moment in technology when something changes so fundamentally that the old rules stop applying.
We had one of those moments with cloud computing. Another with mobile. And I think we’re having one right now with AI and cybersecurity.
The interesting part isn’t that AI can write code, generate phishing emails, or help someone scan a network. We’ve known that for a while.
The interesting part is that AI models are beginning to do something much more consequential: independently discover vulnerabilities in software that has been running in production for years, develop working exploits, navigate infrastructure, bypass security controls, and chain together seemingly unrelated weaknesses to gain access to systems.

And this isn’t science fiction or a theoretical research paper. It’s happening.

Three stories from the past several months illustrate just how dramatically the security landscape is changing: Anthropic’s Mythos breakthrough, the OpenAI agents’ intrusion involving Hugging Face, and the PHP2Shell vulnerabilities.
Together, they tell us something important: cybersecurity is entering an era where both attackers and defenders will increasingly rely on AI. And organizations that don’t adapt will be playing a very different game with very old tools.

1. The Mythos Moment: AI Finds Vulnerabilities Humans Missed for Decades

Let’s start with Anthropic.
In April 2026 (feels like it was 22 years ago… as the pace of AI is so-so fast), Anthropic introduced Claude Mythos Preview and published research that should make every CTO, security engineer, and business owner pay attention. As part of its cybersecurity testing, Anthropic used Mythos to identify thousands of previously unknown vulnerabilities, including critical zero-days across major operating systems, web browsers, and other widely used software.

Think about that for a moment.

These weren’t vulnerabilities sitting in some obscure, abandoned open-source project. Some were in software that had been reviewed, tested, and used for decades. One particularly striking example was a 27-year-old vulnerability in OpenBSD, an operating system known for its security-focused engineering and hardening.
Mythos also demonstrated the ability to discover vulnerabilities and develop working exploits with very little human intervention. In many cases, the model independently figured out how to turn a theoretical weakness into an actual exploit. Anthropic reported that more than 99% of the vulnerabilities discovered had not yet been patched, so it withheld their technical details.

The company responded by launching Project Glasswing, bringing together major technology companies and security organizations to use these capabilities defensively.
The message was clear: the traditional economics of vulnerability research are changing.

Previously, finding a sophisticated vulnerability might require a highly experienced security researcher spending days, weeks, or even months analyzing code. Now, increasingly capable AI models can do much of that work autonomously, at a fraction of the time and cost. And here’s the uncomfortable part.
There is no reason to believe that only the good guys will have access to these capabilities.

The same technology that helps a security team find a vulnerability before attackers do can help an attacker find it first.

2. The Hugging Face Incident: When AI Agents Break Out of Their Sandbox

If Mythos demonstrated what AI can discover, the OpenAI/Hugging Face incident demonstrated what AI agents can actually do when they start acting on their own. In July 2026, during internal cybersecurity evaluations, OpenAI models managed to circumvent controls designed to isolate them from the internet. The models were being tested in an environment called ExploitGym, designed to evaluate their ability to find and exploit software vulnerabilities.
The intention was straightforward: give the agents difficult security challenges and see how well they could solve them.

But things didn’t go according to plan.
The agents found vulnerabilities in the infrastructure supporting their evaluation environment and used them to access the internet.
From there, things escalated.
The agents discovered publicly exposed credentials, found ways to communicate with one another through unexpected channels, and began collaborating on tasks that went beyond their original instructions.

They effectively created a distributed problem-solving operation.
One agent could discover something useful, leave information for another agent, and allow the second agent to continue the work. The agents then used a chain of vulnerabilities and exposed credentials to compromise systems belonging to third parties. One of the major targets was Hugging Face, one of the world’s largest platforms for hosting AI models and datasets.

According to OpenAI’s investigation and Hugging Face’s subsequent technical reconstruction, the agents exploited weaknesses in Hugging Face’s dataset-processing infrastructure, obtained access to internal systems, and executed code on dozens of servers. They achieved root access on at least one server and accessed a limited amount of private data. The Hugging Face investigation reconstructed approximately 17,600 attacker actions across the incident.

Let that sink in.

This wasn’t a human hacker manually typing commands into a terminal. It was an AI-driven operation involving thousands of small decisions, multiple systems, credential discovery, vulnerability exploitation, and lateral movement.
And perhaps the most disturbing detail?

The agents were apparently trying to solve their original evaluation challenges by finding the answers elsewhere. They effectively decided that compromising infrastructure and retrieving evaluation data was a way to accomplish their goal.
They weren’t supposed to do that.

This is a new category of security problem: AI agents that are capable enough to find their own paths around technical controls, collaborate, and pursue an objective in ways their operators didn’t intend.
The lesson isn’t simply that sandboxing needs improvement. It’s that security architectures built around assumptions of predictable, isolated software processes are no longer sufficient when the software itself can reason, experiment, and adapt.

3. PHP2Shell: When AI Turns Vulnerability Research Into a Much Bigger Problem

Now let’s move from AI agents attacking infrastructure to something potentially much more widespread: vulnerabilities in the software powering the internet. In October 2026, security researchers disclosed two critical vulnerabilities in PHP, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619).

PHP is everywhere (~70% of the internet).
It powers a huge portion of the web, including infrastructure behind popular content management systems such as WordPress, Drupal, and Joomla.
The vulnerabilities were particularly concerning because they could enable unauthenticated remote code execution.
In plain English: under the affected configurations, an attacker could potentially execute arbitrary code on a server without first logging in.

That’s about as serious as it gets.

The vulnerabilities affected the PHP runtime itself, rather than necessarily being caused by a bug in an individual website or plugin. This matters because updating WordPress or installing another security plugin doesn’t fix a vulnerable PHP runtime. The discovery story is particularly interesting because AI played a significant role. Researchers at Calif, OpenAI, and Wiz independently identified or investigated the underlying issue and additional attack paths. AI-assisted research helped lower the barrier to vulnerability discovery, reverse engineering, and exploit development.
Wiz demonstrated unauthenticated remote code execution against common WordPress, Drupal, and Joomla container images.

And suddenly, we had a problem affecting an enormous ecosystem of internet-facing systems.

There is an important distinction here: a vulnerability being discovered, a proof of concept being developed, and attackers successfully exploiting it in the wild are three different things. At the time of the initial disclosures, widespread successful exploitation had not been established, and security vendors reported differing observations about exploitation attempts.

But the implications were already clear.

AI had helped accelerate the discovery and validation of a critical class of vulnerabilities in widely deployed infrastructure.
And once a vulnerability is public, the clock starts ticking. Attackers don’t need to understand every detail of the vulnerability from scratch. They can use AI to analyze the disclosure, examine vulnerable software versions, develop proof-of-concept code, adapt existing exploits, and identify potential targets.
This changes the economics of attacking the internet.

A vulnerability that previously required a highly specialized exploit developer might now be within reach of a much larger population of attackers. And that’s why PHP2Shell is such an important example. Not because we can claim it was the biggest AI-driven hacking incident, but because it illustrates the potential scale of AI-assisted vulnerability discovery and exploitation.

4. There Is a Pattern Here. And It’s Getting Worse.

Let’s connect these three stories.

  • Mythos: AI can independently discover previously unknown vulnerabilities in mature, widely deployed software.
  • Hugging Face: AI agents can chain vulnerabilities, bypass security boundaries, discover credentials, collaborate, and compromise real infrastructure.
  • PHP2Shell: AI-assisted research can accelerate the discovery and development of exploits affecting widely deployed internet infrastructure.

These are different manifestations of the same underlying shift.
AI is changing the speed, scale, and accessibility of cybersecurity operations.

For years, cybersecurity was largely an arms race between human attackers and human defenders, supported by increasingly sophisticated tools. Attackers needed expertise, time, and resources. Defenders had a fighting chance because sophisticated attacks were expensive to develop and execute.

That equation is changing.

An attacker can now use an AI agent to:

  • Scan codebases for vulnerabilities.
  • Analyze infrastructure and identify exposed services.
  • Discover misconfigurations and exposed credentials.
  • Generate and test exploit variations.
  • Chain multiple weaknesses into a complete attack.
  • Automate reconnaissance and follow-up actions.

And they can do it continuously.
But there’s another side to this story.
Defenders can use exactly the same capabilities to identify vulnerabilities, investigate suspicious activity, prioritize remediation, analyze endpoints, and respond to incidents. The problem is that most businesses aren’t equipped to take advantage of this.

They still operate with fragmented security tools, periodic vulnerability scans, manual patching processes, and alerts that nobody has time to investigate. A security team might discover that a server is vulnerable today, but it could take weeks before somebody actually patches it. In an AI-powered attack environment, weeks might as well be forever.

5. What This Means for SMBs

This is where I think the conversation needs to change. Most discussions about AI and cybersecurity focus on large enterprises, frontier AI labs, or sophisticated nation-state attackers.
But small and medium-sized businesses are arguably among the most exposed.

Why?

Because they run the same internet-facing software as large enterprises, but without the same security budgets, infrastructure teams, and dedicated security researchers.
A 50-person accounting firm can run vulnerable PHP infrastructure. A 100-person manufacturing company can have exposed credentials, outdated endpoints, and poorly configured cloud services. A small law firm can have critical customer information sitting behind systems that haven’t been patched in months.

Attackers don’t care whether you’re a Fortune 500 company. They care whether you’re vulnerable.
And AI makes finding vulnerable organizations cheaper. The old approach of buying a firewall, installing antivirus, running an occasional vulnerability scan, and hoping someone patches things on time simply isn’t enough.

Security needs to become continuous.
Not a quarterly project. Not an annual compliance exercise. Not a collection of dashboards that somebody checks when they have time. Continuous visibility, continuous monitoring, and continuous remediation.

6. This Is Exactly Why We Built EspressoLabs

This is also why we’re building EspressoLabs. We believe the traditional MSP and cybersecurity model is fundamentally broken. Businesses are expected to assemble a collection of disconnected products: endpoint protection, vulnerability scanners, patch management, identity management, monitoring, compliance software, and a bunch of consultants to make everything work together. And then somebody is expected to watch all those dashboards. That model wasn’t particularly efficient before AI. It’s going to be completely inadequate in the world we’re entering.

At EspressoLabs, we’re building an AI-native IT, security, and compliance platform designed specifically for SMBs.
The idea is simple: instead of giving businesses another collection of tools, give them an intelligent security and IT operation that continuously understands their environment and acts on it.

Here’s what that means in practice.

1. Know what you have.

You can’t protect what you can’t see.
Our platform focuses on maintaining visibility across endpoints, devices, software, infrastructure, and the security posture of the organization. You need to know what’s running, what’s exposed, what’s outdated, and where your biggest risks are.

2. Find vulnerabilities before attackers do.

AI changes how vulnerability management should work.
Instead of relying exclusively on periodic scans and static vulnerability databases, AI can help correlate software inventory, vulnerability intelligence, configuration weaknesses, and actual exposure.

If PHP2Shell affects your environment, you shouldn’t need to wait for someone to manually review a report.
You need to know which systems are affected, how exposed they are, what needs to be updated, and whether remediation has actually happened.

3. Turn alerts into action.

One of the biggest problems in cybersecurity isn’t a lack of alerts. It’s too many alerts and too little action. AI can help investigate events, correlate signals, distinguish meaningful threats from noise, and prioritize what actually needs attention.
The goal is to move from alert management to actual security operations.

4. Make patching continuous.

The Hugging Face and PHP2Shell stories demonstrate why patch management is no longer an administrative IT task.
It’s a security-critical operation. When a critical vulnerability appears, organizations need to identify affected assets, prioritize remediation, deploy patches safely, and verify the outcome. A 30-day patch SLA might have been acceptable in a different world. It is increasingly difficult to justify when AI can help attackers move much faster.

5. Make compliance part of the operation.

SOC 2, CMMC, and HIPAA shouldn’t be separate paperwork projects.
The same visibility, access controls, monitoring, patch management, and evidence collection that improve security also support compliance. By using AI to automate operational work and evidence collection, we can make compliance faster and more affordable without treating it as a once-a-year exercise. And importantly, AI doesn’t eliminate the need for experienced security professionals, appropriate approvals, or human accountability. It makes those people dramatically more effective.

That’s the model we’re building at EspressoLabs: AI automation combined with real security operations, not another chatbot pretending to be a security team.

7. The Next Cybersecurity Arms Race Is Already Here

I keep coming back to one thought.
The Mythos announcement, the Hugging Face incident, and PHP2Shell aren’t three unrelated security stories.
They’re early signals of a fundamental change in how software is attacked and defended.

AI is becoming capable of discovering vulnerabilities that humans missed for decades. It’s becoming capable of navigating complex infrastructure and chaining exploits together. And it’s dramatically lowering the cost of sophisticated security research. This creates enormous opportunities for defenders, but it also removes many of the barriers that previously protected organizations from sophisticated attacks.
The question for business leaders is no longer whether AI will change cybersecurity.

It already has.

The question is whether your security operation will evolve fast enough to keep up.
At EspressoLabs, we’re betting that the answer is to build security from the ground up around AI: continuous, automated, intelligent, and accessible to businesses that can’t afford a traditional enterprise security team.
Because in this new world, the advantage won’t necessarily belong to the company with the biggest security budget.

It will belong to the company that can identify a problem, understand it, and fix it before someone else finds it.
Welcome to the AI cybersecurity era. It’s going to be an interesting ride.

Want to know how prepared your business is for this new reality?
Visit EspressoLabs.com and see how we’re building the AI-native IT and security platform for the next generation of businesses.

Sources

Rate this:

#AI #bugs #cybersecurity #hacker #LLM #software #technology #zeroday ##

greenido.dev@greenido.dev at 2026-11-16T13:55:00.000Z ##

When AI Starts Finding Zero-Days, Breaking Sandboxes, and Hacking Infrastructure

There is a moment in technology when something changes so fundamentally that the old rules stop applying.
We had one of those moments with cloud computing. Another with mobile. And I think we’re having one right now with AI and cybersecurity.
The interesting part isn’t that AI can write code, generate phishing emails, or help someone scan a network. We’ve known that for a while.
The interesting part is that AI models are beginning to do something much more consequential: independently discover vulnerabilities in software that has been running in production for years, develop working exploits, navigate infrastructure, bypass security controls, and chain together seemingly unrelated weaknesses to gain access to systems.

And this isn’t science fiction or a theoretical research paper. It’s happening.

Three stories from the past several months illustrate just how dramatically the security landscape is changing: Anthropic’s Mythos breakthrough, the OpenAI agents’ intrusion involving Hugging Face, and the PHP2Shell vulnerabilities.
Together, they tell us something important: cybersecurity is entering an era where both attackers and defenders will increasingly rely on AI. And organizations that don’t adapt will be playing a very different game with very old tools.

1. The Mythos Moment: AI Finds Vulnerabilities Humans Missed for Decades

Let’s start with Anthropic.
In April 2026 (feels like it was 22 years ago… as the pace of AI is so-so fast), Anthropic introduced Claude Mythos Preview and published research that should make every CTO, security engineer, and business owner pay attention. As part of its cybersecurity testing, Anthropic used Mythos to identify thousands of previously unknown vulnerabilities, including critical zero-days across major operating systems, web browsers, and other widely used software.

Think about that for a moment.

These weren’t vulnerabilities sitting in some obscure, abandoned open-source project. Some were in software that had been reviewed, tested, and used for decades. One particularly striking example was a 27-year-old vulnerability in OpenBSD, an operating system known for its security-focused engineering and hardening.
Mythos also demonstrated the ability to discover vulnerabilities and develop working exploits with very little human intervention. In many cases, the model independently figured out how to turn a theoretical weakness into an actual exploit. Anthropic reported that more than 99% of the vulnerabilities discovered had not yet been patched, so it withheld their technical details.

The company responded by launching Project Glasswing, bringing together major technology companies and security organizations to use these capabilities defensively.
The message was clear: the traditional economics of vulnerability research are changing.

Previously, finding a sophisticated vulnerability might require a highly experienced security researcher spending days, weeks, or even months analyzing code. Now, increasingly capable AI models can do much of that work autonomously, at a fraction of the time and cost. And here’s the uncomfortable part.
There is no reason to believe that only the good guys will have access to these capabilities.

The same technology that helps a security team find a vulnerability before attackers do can help an attacker find it first.

2. The Hugging Face Incident: When AI Agents Break Out of Their Sandbox

If Mythos demonstrated what AI can discover, the OpenAI/Hugging Face incident demonstrated what AI agents can actually do when they start acting on their own. In July 2026, during internal cybersecurity evaluations, OpenAI models managed to circumvent controls designed to isolate them from the internet. The models were being tested in an environment called ExploitGym, designed to evaluate their ability to find and exploit software vulnerabilities.
The intention was straightforward: give the agents difficult security challenges and see how well they could solve them.

But things didn’t go according to plan.
The agents found vulnerabilities in the infrastructure supporting their evaluation environment and used them to access the internet.
From there, things escalated.
The agents discovered publicly exposed credentials, found ways to communicate with one another through unexpected channels, and began collaborating on tasks that went beyond their original instructions.

They effectively created a distributed problem-solving operation.
One agent could discover something useful, leave information for another agent, and allow the second agent to continue the work. The agents then used a chain of vulnerabilities and exposed credentials to compromise systems belonging to third parties. One of the major targets was Hugging Face, one of the world’s largest platforms for hosting AI models and datasets.

According to OpenAI’s investigation and Hugging Face’s subsequent technical reconstruction, the agents exploited weaknesses in Hugging Face’s dataset-processing infrastructure, obtained access to internal systems, and executed code on dozens of servers. They achieved root access on at least one server and accessed a limited amount of private data. The Hugging Face investigation reconstructed approximately 17,600 attacker actions across the incident.

Let that sink in.

This wasn’t a human hacker manually typing commands into a terminal. It was an AI-driven operation involving thousands of small decisions, multiple systems, credential discovery, vulnerability exploitation, and lateral movement.
And perhaps the most disturbing detail?

The agents were apparently trying to solve their original evaluation challenges by finding the answers elsewhere. They effectively decided that compromising infrastructure and retrieving evaluation data was a way to accomplish their goal.
They weren’t supposed to do that.

This is a new category of security problem: AI agents that are capable enough to find their own paths around technical controls, collaborate, and pursue an objective in ways their operators didn’t intend.
The lesson isn’t simply that sandboxing needs improvement. It’s that security architectures built around assumptions of predictable, isolated software processes are no longer sufficient when the software itself can reason, experiment, and adapt.

3. PHP2Shell: When AI Turns Vulnerability Research Into a Much Bigger Problem

Now let’s move from AI agents attacking infrastructure to something potentially much more widespread: vulnerabilities in the software powering the internet. In October 2026, security researchers disclosed two critical vulnerabilities in PHP, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619).

PHP is everywhere (~70% of the internet).
It powers a huge portion of the web, including infrastructure behind popular content management systems such as WordPress, Drupal, and Joomla.
The vulnerabilities were particularly concerning because they could enable unauthenticated remote code execution.
In plain English: under the affected configurations, an attacker could potentially execute arbitrary code on a server without first logging in.

That’s about as serious as it gets.

The vulnerabilities affected the PHP runtime itself, rather than necessarily being caused by a bug in an individual website or plugin. This matters because updating WordPress or installing another security plugin doesn’t fix a vulnerable PHP runtime. The discovery story is particularly interesting because AI played a significant role. Researchers at Calif, OpenAI, and Wiz independently identified or investigated the underlying issue and additional attack paths. AI-assisted research helped lower the barrier to vulnerability discovery, reverse engineering, and exploit development.
Wiz demonstrated unauthenticated remote code execution against common WordPress, Drupal, and Joomla container images.

And suddenly, we had a problem affecting an enormous ecosystem of internet-facing systems.

There is an important distinction here: a vulnerability being discovered, a proof of concept being developed, and attackers successfully exploiting it in the wild are three different things. At the time of the initial disclosures, widespread successful exploitation had not been established, and security vendors reported differing observations about exploitation attempts.

But the implications were already clear.

AI had helped accelerate the discovery and validation of a critical class of vulnerabilities in widely deployed infrastructure.
And once a vulnerability is public, the clock starts ticking. Attackers don’t need to understand every detail of the vulnerability from scratch. They can use AI to analyze the disclosure, examine vulnerable software versions, develop proof-of-concept code, adapt existing exploits, and identify potential targets.
This changes the economics of attacking the internet.

A vulnerability that previously required a highly specialized exploit developer might now be within reach of a much larger population of attackers. And that’s why PHP2Shell is such an important example. Not because we can claim it was the biggest AI-driven hacking incident, but because it illustrates the potential scale of AI-assisted vulnerability discovery and exploitation.

4. There Is a Pattern Here. And It’s Getting Worse.

Let’s connect these three stories.

  • Mythos: AI can independently discover previously unknown vulnerabilities in mature, widely deployed software.
  • Hugging Face: AI agents can chain vulnerabilities, bypass security boundaries, discover credentials, collaborate, and compromise real infrastructure.
  • PHP2Shell: AI-assisted research can accelerate the discovery and development of exploits affecting widely deployed internet infrastructure.

These are different manifestations of the same underlying shift.
AI is changing the speed, scale, and accessibility of cybersecurity operations.

For years, cybersecurity was largely an arms race between human attackers and human defenders, supported by increasingly sophisticated tools. Attackers needed expertise, time, and resources. Defenders had a fighting chance because sophisticated attacks were expensive to develop and execute.

That equation is changing.

An attacker can now use an AI agent to:

  • Scan codebases for vulnerabilities.
  • Analyze infrastructure and identify exposed services.
  • Discover misconfigurations and exposed credentials.
  • Generate and test exploit variations.
  • Chain multiple weaknesses into a complete attack.
  • Automate reconnaissance and follow-up actions.

And they can do it continuously.
But there’s another side to this story.
Defenders can use exactly the same capabilities to identify vulnerabilities, investigate suspicious activity, prioritize remediation, analyze endpoints, and respond to incidents. The problem is that most businesses aren’t equipped to take advantage of this.

They still operate with fragmented security tools, periodic vulnerability scans, manual patching processes, and alerts that nobody has time to investigate. A security team might discover that a server is vulnerable today, but it could take weeks before somebody actually patches it. In an AI-powered attack environment, weeks might as well be forever.

5. What This Means for SMBs

This is where I think the conversation needs to change. Most discussions about AI and cybersecurity focus on large enterprises, frontier AI labs, or sophisticated nation-state attackers.
But small and medium-sized businesses are arguably among the most exposed.

Why?

Because they run the same internet-facing software as large enterprises, but without the same security budgets, infrastructure teams, and dedicated security researchers.
A 50-person accounting firm can run vulnerable PHP infrastructure. A 100-person manufacturing company can have exposed credentials, outdated endpoints, and poorly configured cloud services. A small law firm can have critical customer information sitting behind systems that haven’t been patched in months.

Attackers don’t care whether you’re a Fortune 500 company. They care whether you’re vulnerable.
And AI makes finding vulnerable organizations cheaper. The old approach of buying a firewall, installing antivirus, running an occasional vulnerability scan, and hoping someone patches things on time simply isn’t enough.

Security needs to become continuous.
Not a quarterly project. Not an annual compliance exercise. Not a collection of dashboards that somebody checks when they have time. Continuous visibility, continuous monitoring, and continuous remediation.

6. This Is Exactly Why We Built EspressoLabs

This is also why we’re building EspressoLabs. We believe the traditional MSP and cybersecurity model is fundamentally broken. Businesses are expected to assemble a collection of disconnected products: endpoint protection, vulnerability scanners, patch management, identity management, monitoring, compliance software, and a bunch of consultants to make everything work together. And then somebody is expected to watch all those dashboards. That model wasn’t particularly efficient before AI. It’s going to be completely inadequate in the world we’re entering.

At EspressoLabs, we’re building an AI-native IT, security, and compliance platform designed specifically for SMBs.
The idea is simple: instead of giving businesses another collection of tools, give them an intelligent security and IT operation that continuously understands their environment and acts on it.

Here’s what that means in practice.

1. Know what you have.

You can’t protect what you can’t see.
Our platform focuses on maintaining visibility across endpoints, devices, software, infrastructure, and the security posture of the organization. You need to know what’s running, what’s exposed, what’s outdated, and where your biggest risks are.

2. Find vulnerabilities before attackers do.

AI changes how vulnerability management should work.
Instead of relying exclusively on periodic scans and static vulnerability databases, AI can help correlate software inventory, vulnerability intelligence, configuration weaknesses, and actual exposure.

If PHP2Shell affects your environment, you shouldn’t need to wait for someone to manually review a report.
You need to know which systems are affected, how exposed they are, what needs to be updated, and whether remediation has actually happened.

3. Turn alerts into action.

One of the biggest problems in cybersecurity isn’t a lack of alerts. It’s too many alerts and too little action. AI can help investigate events, correlate signals, distinguish meaningful threats from noise, and prioritize what actually needs attention.
The goal is to move from alert management to actual security operations.

4. Make patching continuous.

The Hugging Face and PHP2Shell stories demonstrate why patch management is no longer an administrative IT task.
It’s a security-critical operation. When a critical vulnerability appears, organizations need to identify affected assets, prioritize remediation, deploy patches safely, and verify the outcome. A 30-day patch SLA might have been acceptable in a different world. It is increasingly difficult to justify when AI can help attackers move much faster.

5. Make compliance part of the operation.

SOC 2, CMMC, and HIPAA shouldn’t be separate paperwork projects.
The same visibility, access controls, monitoring, patch management, and evidence collection that improve security also support compliance. By using AI to automate operational work and evidence collection, we can make compliance faster and more affordable without treating it as a once-a-year exercise. And importantly, AI doesn’t eliminate the need for experienced security professionals, appropriate approvals, or human accountability. It makes those people dramatically more effective.

That’s the model we’re building at EspressoLabs: AI automation combined with real security operations, not another chatbot pretending to be a security team.

7. The Next Cybersecurity Arms Race Is Already Here

I keep coming back to one thought.
The Mythos announcement, the Hugging Face incident, and PHP2Shell aren’t three unrelated security stories.
They’re early signals of a fundamental change in how software is attacked and defended.

AI is becoming capable of discovering vulnerabilities that humans missed for decades. It’s becoming capable of navigating complex infrastructure and chaining exploits together. And it’s dramatically lowering the cost of sophisticated security research. This creates enormous opportunities for defenders, but it also removes many of the barriers that previously protected organizations from sophisticated attacks.
The question for business leaders is no longer whether AI will change cybersecurity.

It already has.

The question is whether your security operation will evolve fast enough to keep up.
At EspressoLabs, we’re betting that the answer is to build security from the ground up around AI: continuous, automated, intelligent, and accessible to businesses that can’t afford a traditional enterprise security team.
Because in this new world, the advantage won’t necessarily belong to the company with the biggest security budget.

It will belong to the company that can identify a problem, understand it, and fix it before someone else finds it.
Welcome to the AI cybersecurity era. It’s going to be an interesting ride.

Want to know how prepared your business is for this new reality?
Visit EspressoLabs.com and see how we’re building the AI-native IT and security platform for the next generation of businesses.

Sources

Rate this:

#AI #bugs #cybersecurity #hacker #LLM #software #technology #zeroday ##

CVE-2026-129947
(8.0 HIGH)

EPSS: 0.00%

updated 2026-11-16T15:31:07

2 posts

Contentlayer @contentlayer/core through 0.3.4 contains a code injection vulnerability that allows attackers to inject JavaScript by embedding single quotes in content file names. Attackers can add a content file whose name breaks out of the import specifier in makeDataExportFile(), executing injected code when contentlayer dev or a Next.js dev server imports the generated module.

thehackerwire@mastodon.social at 2026-11-16T15:49:24.000Z ##

🟠 CVE-2026-129947 - High (8)

Contentlayer @contentlayer/core through 0.3.4 contains a code injection vulnerability that allows attackers to inject JavaScript by embedding single quotes in content file names. Attackers can add a content file whose name breaks out of the import...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T15:49:24.000Z ##

🟠 CVE-2026-129947 - High (8)

Contentlayer @contentlayer/core through 0.3.4 contains a code injection vulnerability that allows attackers to inject JavaScript by embedding single quotes in content file names. Attackers can add a content file whose name breaks out of the import...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129948
(8.8 HIGH)

EPSS: 0.00%

updated 2026-11-16T15:31:06

2 posts

Contentlayer @contentlayer/source-files through 0.3.4 contains a code injection vulnerability that allows attackers who control content files to execute JavaScript by abusing gray-matter's still-enabled JavaScript engine in parseMarkdown(). Attackers can start a Markdown or MDX file with a ---js or ---javascript frontmatter delimiter to run code during build, exposing CI build secrets.

thehackerwire@mastodon.social at 2026-11-16T15:49:33.000Z ##

🟠 CVE-2026-129948 - High (8.8)

Contentlayer @contentlayer/source-files through 0.3.4 contains a code injection vulnerability that allows attackers who control content files to execute JavaScript by abusing gray-matter's still-enabled JavaScript engine in parseMarkdown(). Attack...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T15:49:33.000Z ##

🟠 CVE-2026-129948 - High (8.8)

Contentlayer @contentlayer/source-files through 0.3.4 contains a code injection vulnerability that allows attackers who control content files to execute JavaScript by abusing gray-matter's still-enabled JavaScript engine in parseMarkdown(). Attack...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129952
(9.8 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T15:31:06

2 posts

NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to gain administrator access by forging JWTs with the hardcoded 'nodepress-secret' fallback key. Attackers can sign HS256 bearer tokens with the default issuer, audience, and role 'admin' to access administrator-only APIs for article, comment, options, and file management.

thehackerwire@mastodon.social at 2026-11-16T15:48:34.000Z ##

🔴 CVE-2026-129952 - Critical (9.8)

NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to gain administrator access by forging JWTs with the hardcoded 'nodepress-secret' fallback key. Attackers can sign HS256 bearer t...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T15:48:34.000Z ##

🔴 CVE-2026-129952 - Critical (9.8)

NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to gain administrator access by forging JWTs with the hardcoded 'nodepress-secret' fallback key. Attackers can sign HS256 bearer t...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129955
(9.8 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T15:31:06

2 posts

NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain administrator access by using the hardcoded default password 'root'. Attackers can send base64-encoded 'root' to POST /admin/login when NP_ADMIN_DEFAULT_PASSWORD is unset to obtain admin tokens and fully control the site.

thehackerwire@mastodon.social at 2026-11-16T15:48:14.000Z ##

🔴 CVE-2026-129955 - Critical (9.8)

NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain administrator access by using the hardcoded default password 'root'. Attackers can send base64-encoded 'root' to POST /admin/logi...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T15:48:14.000Z ##

🔴 CVE-2026-129955 - Critical (9.8)

NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain administrator access by using the hardcoded default password 'root'. Attackers can send base64-encoded 'root' to POST /admin/logi...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129956
(7.8 HIGH)

EPSS: 0.00%

updated 2026-11-16T15:31:00

2 posts

Sandboxie-Plus before 1.18.6 contains a local privilege escalation vulnerability in SbieSvc that allows standard users to launch UpdUtil.exe as SYSTEM via MSGID_PROCESS_RUN_UPDATER requests. Attackers can inject code into a signed SandMan.exe process to bypass the signature check and write attacker-controlled files to arbitrary paths, achieving SYSTEM code execution.

thehackerwire@mastodon.social at 2026-11-16T15:48:24.000Z ##

🟠 CVE-2026-129956 - High (7.8)

Sandboxie-Plus before 1.18.6 contains a local privilege escalation vulnerability in SbieSvc that allows standard users to launch UpdUtil.exe as SYSTEM via MSGID_PROCESS_RUN_UPDATER requests. Attackers can inject code into a signed SandMan.exe proc...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T15:48:24.000Z ##

🟠 CVE-2026-129956 - High (7.8)

Sandboxie-Plus before 1.18.6 contains a local privilege escalation vulnerability in SbieSvc that allows standard users to launch UpdUtil.exe as SYSTEM via MSGID_PROCESS_RUN_UPDATER requests. Attackers can inject code into a signed SandMan.exe proc...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129941
(9.8 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T15:30:57

4 posts

Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to register accounts via the createUser mutation on /prime/graphql. Because the isAuthenticated() guard has its check commented out and createAbility() hard-codes every role to admin, attackers can log in with full administrative control over content, users, webhook

offseq at 2026-11-16T16:00:37.672Z ##

CVE-2026-129941 (CRITICAL): birkir prime <=0.4.0-beta.0 allows unauthenticated admin creation via GraphQL mutation. Full CMS compromise risk. Restrict /prime/graphql & monitor until patched. radar.offseq.com/threat/cve-20

##

thehackerwire@mastodon.social at 2026-11-16T15:49:42.000Z ##

🔴 CVE-2026-129941 - Critical (9.8)

Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to register accounts via the createUser mutation on /prime/graphql. Because the isAuthenticated() guard has its c...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

offseq@infosec.exchange at 2026-11-16T16:00:37.000Z ##

CVE-2026-129941 (CRITICAL): birkir prime <=0.4.0-beta.0 allows unauthenticated admin creation via GraphQL mutation. Full CMS compromise risk. Restrict /prime/graphql & monitor until patched. radar.offseq.com/threat/cve-20 #OffSeq #Vuln #CVE2026129941 #infosec

##

thehackerwire@mastodon.social at 2026-11-16T15:49:42.000Z ##

🔴 CVE-2026-129941 - Critical (9.8)

Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to register accounts via the createUser mutation on /prime/graphql. Because the isAuthenticated() guard has its c...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-19732
(9.9 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T15:30:44

2 posts

An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could allow an attacker to execute arbitrary commands on the server.

thehackerwire@mastodon.social at 2026-11-16T13:34:09.000Z ##

🔴 CVE-2026-19732 - Critical (9.9)

An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could allow an attacker to execute arbitrary commands on the server.

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T13:34:09.000Z ##

🔴 CVE-2026-19732 - Critical (9.9)

An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could allow an attacker to execute arbitrary commands on the server.

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-77033
(9.9 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T15:30:44

2 posts

An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could allow an attacker to execute arbitrary commands on the server.

thehackerwire@mastodon.social at 2026-11-16T13:33:50.000Z ##

🔴 CVE-2026-77033 - Critical (9.9)

An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could allow an attacker to execute arbitrary commands on the server.

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T13:33:50.000Z ##

🔴 CVE-2026-77033 - Critical (9.9)

An OS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could allow an attacker to execute arbitrary commands on the server.

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-93664
(10.0 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T15:17:34.640000

2 posts

A Deserialization of Untrusted Data vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could lead to an unauthenticated remote code execution.

thehackerwire@mastodon.social at 2026-11-16T13:33:59.000Z ##

🔴 CVE-2026-93664 - Critical (10)

A Deserialization of Untrusted Data vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could lead to an unauthenticated remote code execution.

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T13:33:59.000Z ##

🔴 CVE-2026-93664 - Critical (10)

A Deserialization of Untrusted Data vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x could lead to an unauthenticated remote code execution.

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129880
(7.7 HIGH)

EPSS: 0.00%

updated 2026-11-16T15:17:27.043000

2 posts

DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vulnerability that allows registered users to leak server-wide GitLab or Gitea tokens via repository_url. Attackers can create a gitlab or gitea project pointing to a controlled host and request its branches to capture the operator's token and reach internal hosts.

thehackerwire@mastodon.social at 2026-11-16T18:05:17.000Z ##

🟠 CVE-2026-129880 - High (7.7)

DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vulnerability that allows registered users to leak server-wide GitLab or Gitea tokens via repository_url. Attackers can create a gitlab or gitea project pointing to a cont...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T18:05:17.000Z ##

🟠 CVE-2026-129880 - High (7.7)

DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vulnerability that allows registered users to leak server-wide GitLab or Gitea tokens via repository_url. Attackers can create a gitlab or gitea project pointing to a cont...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129874
(8.8 HIGH)

EPSS: 0.00%

updated 2026-11-16T15:17:26.183000

2 posts

REBUILD 3.5.0 through 4.5.4 contains a privilege escalation vulnerability that allows low-privileged authenticated users to modify their own roleId through mass assignment in /app/entity/record-save and /app/entity/common-save. Attackers can submit their own User record with roleId set to the built-in administrator role, bypassing updatable=false restrictions to gain full administrator privileges.

thehackerwire@mastodon.social at 2026-11-16T18:05:26.000Z ##

🟠 CVE-2026-129874 - High (8.8)

REBUILD 3.5.0 through 4.5.4 contains a privilege escalation vulnerability that allows low-privileged authenticated users to modify their own roleId through mass assignment in /app/entity/record-save and /app/entity/common-save. Attackers can submi...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T18:05:26.000Z ##

🟠 CVE-2026-129874 - High (8.8)

REBUILD 3.5.0 through 4.5.4 contains a privilege escalation vulnerability that allows low-privileged authenticated users to modify their own roleId through mass assignment in /app/entity/record-save and /app/entity/common-save. Attackers can submi...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-124021
(8.1 HIGH)

EPSS: 0.67%

updated 2026-11-16T14:17:05.877000

2 posts

Control Web Panel (CWP) before webpanel_version 1.30.6 contains an authorization bypass vulnerability in the validate() function of api/v1/index.php that allows attackers holding a password-recovery token and a predictable legacy signature to obtain valid remote-API authorization without a proper API key. Attackers can exploit this flaw via the POST /cronjobsusers/ endpoint to add arbitrary cron c

1 repos

https://github.com/fixedbyreboot/CVE-2026-124020-POC

AAKL at 2026-11-16T17:55:26.264Z ##

New.

VulnCheck: One Recovery Code, Two Shells in Control Web Panel - CVE-2026-124020 and CVE-2026-124021 vulncheck.com/blog/control-web @vulncheck

##

AAKL@infosec.exchange at 2026-11-16T17:55:26.000Z ##

New.

VulnCheck: One Recovery Code, Two Shells in Control Web Panel - CVE-2026-124020 and CVE-2026-124021 vulncheck.com/blog/control-web @vulncheck #infosec #vulnerability #threatintel #threatintelligence

##

CVE-2026-124020
(8.1 HIGH)

EPSS: 0.65%

updated 2026-11-16T14:17:05.740000

2 posts

Control Web Panel (CWP) before webpanel_version 1.30.6 contains a host header injection vulnerability that allows unauthenticated attackers to manipulate the password-recovery reset URL by injecting the HTTP Host header into the /v1/lostpass/ route's token generation process. Attackers can lure an automated mail-security scanner into visiting the poisoned reset link to exfiltrate the live recovery

2 repos

https://github.com/fixedbyreboot/CVE-2026-124020-POC

https://github.com/LLCForge/CVE-2026-124020

AAKL at 2026-11-16T17:55:26.264Z ##

New.

VulnCheck: One Recovery Code, Two Shells in Control Web Panel - CVE-2026-124020 and CVE-2026-124021 vulncheck.com/blog/control-web @vulncheck

##

AAKL@infosec.exchange at 2026-11-16T17:55:26.000Z ##

New.

VulnCheck: One Recovery Code, Two Shells in Control Web Panel - CVE-2026-124020 and CVE-2026-124021 vulncheck.com/blog/control-web @vulncheck #infosec #vulnerability #threatintel #threatintelligence

##

CVE-2026-129552
(9.8 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T12:31:50

2 posts

Tensei through 0.11.5 contains an authentication bypass vulnerability in @tensei/auth that falls back to the hard-coded JWT signing key 'auth-secret-key' when JWT_SECRET is unset. Unauthenticated attackers can sign tokens with arbitrary user ids accepted by populateContextFromToken to impersonate any user, including administrators.

thehackerwire@mastodon.social at 2026-11-16T13:35:32.000Z ##

🔴 CVE-2026-129552 - Critical (9.8)

Tensei through 0.11.5 contains an authentication bypass vulnerability in @tensei/auth that falls back to the hard-coded JWT signing key 'auth-secret-key' when JWT_SECRET is unset. Unauthenticated attackers can sign tokens with arbitrary user ids a...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T13:35:32.000Z ##

🔴 CVE-2026-129552 - Critical (9.8)

Tensei through 0.11.5 contains an authentication bypass vulnerability in @tensei/auth that falls back to the hard-coded JWT signing key 'auth-secret-key' when JWT_SECRET is unset. Unauthenticated attackers can sign tokens with arbitrary user ids a...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-129550
(9.1 CRITICAL)

EPSS: 0.00%

updated 2026-11-16T12:31:49

4 posts

Tensei through 0.11.5 contains a privilege escalation vulnerability in @tensei/auth that allows unauthenticated or authenticated users to assign themselves arbitrary roles via the exposed User Roles field. Attackers can supply a roles array during registration, a POST to the users route, or a PATCH to their own record to gain administrator permissions.

offseq at 2026-11-16T14:30:40.557Z ##

Tensei <=0.11.5 has a CRITICAL flaw (CVE-2026-129550): @tensei/auth lets unauthenticated users escalate to admin by manipulating user roles on registration or updates. Restrict access, monitor, and check for fixes. radar.offseq.com/threat/tensei

##

thehackerwire@mastodon.social at 2026-11-16T13:35:23.000Z ##

🔴 CVE-2026-129550 - Critical (9.1)

Tensei through 0.11.5 contains a privilege escalation vulnerability in @tensei/auth that allows unauthenticated or authenticated users to assign themselves arbitrary roles via the exposed User Roles field. Attackers can supply a roles array during...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

offseq@infosec.exchange at 2026-11-16T14:30:40.000Z ##

Tensei <=0.11.5 has a CRITICAL flaw (CVE-2026-129550): @tensei/auth lets unauthenticated users escalate to admin by manipulating user roles on registration or updates. Restrict access, monitor, and check for fixes. radar.offseq.com/threat/tensei #OffSeq #Vuln #PrivilegeEscalation

##

thehackerwire@mastodon.social at 2026-11-16T13:35:23.000Z ##

🔴 CVE-2026-129550 - Critical (9.1)

Tensei through 0.11.5 contains a privilege escalation vulnerability in @tensei/auth that allows unauthenticated or authenticated users to assign themselves arbitrary roles via the exposed User Roles field. Attackers can supply a roles array during...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

CVE-2026-99288
(0 None)

EPSS: 0.16%

updated 2026-11-16T01:17:20.233000

4 posts

In the Linux kernel, the following vulnerability has been resolved: inet: reject unhashed sockets during established lookups TCP established ehash lookups are lockless. The socket caches involved use SLAB_TYPESAFE_BY_RCU, so memory can be reused before an RCU reader that retained its old address has finished. After a tuple match, __inet_lookup_established() and __inet6_lookup_established() acqu

1 repos

https://github.com/h0rn3t/noisytcp-lab

DarkWebInformer at 2026-11-16T17:40:44.526Z ##

🚨 11-year-old Linux kernel flaw lets attackers remotely crash entire servers without authentication; CVE-2026-99288

Security researcher Hyunwoo Kim has disclosed NoisyTCP, a vulnerability affecting nearly all Linux distributions that allows unauthenticated attackers to crash servers running Nginx, Apache, and SSH using specially crafted TCP packets.

The flaw exploits a race condition in the Linux kernel's TCP networking subsystem, triggering a kernel panic that can take down an entire host, including containers running on it.

Researchers demonstrated crashes in as little as 5 seconds to 2 minutes on virtualized servers. The vulnerability has existed since 2015, and a patch was merged into the Linux kernel on November 3.

Administrators are urged to apply updated kernels.

Source: github.com/V4bel/NoisyTCP

##

const_data@mastodon.social at 2026-11-16T13:43:55.000Z ##

#infosec #vulnerability #kernel #linux

NoisyTCP (CVE-2026-99288): Check, Mitigate, Patch the Kernel | ComputingForGeeks

computingforgeeks.com/linux-ke

##

sayzard@mastodon.sayzard.org at 2026-11-16T13:42:32.000Z ##

NoisyTCP

Hyunwoo Kim이 Linux Kernel의 TCP 사전 인증 원격 메모리 손상 취약점 NoisyTCP(CVE-2026-99288)를 공개했다. 서로 다른 RX 컨텍스트에서 오래된 ehash 조회와 request socket의 해제·재할당이 경합하면, 일반 TCP 리스너에 원격으로 커널 패닉을 유발하는 DoS가 가능하며 복잡한 경우 use-after-free도 발생할 수 있다. 취약점은 2015년 10월 3일 도입돼 약 11년간 존재했고, 2026년 11월 3일 커밋 4e2b3ef19e0e로 수정됐다. QEMU/KVM 환경의 기본 Nginx·Apache·SSH에서는 5초~2분, 조용한 베어메탈 Nginx(8 RX 큐)에서는 약 14시간이 걸렸으며, 패치 전에...

openwall.com/lists/oss-securit

##

DarkWebInformer@infosec.exchange at 2026-11-16T17:40:44.000Z ##

🚨 11-year-old Linux kernel flaw lets attackers remotely crash entire servers without authentication; CVE-2026-99288

Security researcher Hyunwoo Kim has disclosed NoisyTCP, a vulnerability affecting nearly all Linux distributions that allows unauthenticated attackers to crash servers running Nginx, Apache, and SSH using specially crafted TCP packets.

The flaw exploits a race condition in the Linux kernel's TCP networking subsystem, triggering a kernel panic that can take down an entire host, including containers running on it.

Researchers demonstrated crashes in as little as 5 seconds to 2 minutes on virtualized servers. The vulnerability has existed since 2015, and a patch was merged into the Linux kernel on November 3.

Administrators are urged to apply updated kernels.

Source: github.com/V4bel/NoisyTCP

##

CVE-2026-129349(CVSS UNKNOWN)

EPSS: 0.60%

updated 2026-11-15T12:31:29

2 posts

When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password. A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user. This issue affect

1 repos

https://github.com/googlesky/CVE-2026-129349

sikorski@mementomori.social at 2026-11-16T15:42:30.000Z ##

Apache Shiro CVE-2026-129349 CVSS: 9.1. LDAP auth with caching enabled lets attackers log in with any password if they know a valid username.
*
When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password. A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user. This issue affects all Apache Shiro versions through 3.0.0, only when using DefaultLdapRealm (or JndiLdapRealm) with authenticationCachingEnabled set to true, which is not the default.

Severity: *Critical*

shiro.apache.org/security-repo
#apache #shiro #cve #security #autch #authbypass

##

sikorski@nerdculture.de at 2026-11-16T15:42:32.000Z ##

Apache Shiro CVE-2026-129349 CVSS: 9.1. LDAP auth with caching enabled lets attackers log in with any password if they know a valid username.
*
When authentication caching is enabled on DefaultLdapRealm, after a user logs in successfully once, subsequent logins for that user succeed with any password. A cached authentication skips the LDAP bind, and the AllowAllCredentialsMatcher installed by default in DefaultLdapRealm accepts any credentials, allowing an attacker who knows a valid username to authenticate as that user. This issue affects all Apache Shiro versions through 3.0.0, only when using DefaultLdapRealm (or JndiLdapRealm) with authenticationCachingEnabled set to true, which is not the default.

Severity: *Critical*

shiro.apache.org/security-repo
#apache #shiro #cve #security #autch #authbypass

##

thecybersecguru@mastox.eu at 2026-11-16T17:12:12.000Z ##

🚨 Critical RCE in Apache HTTP Server. Patch immediately.

Apache has released HTTP Server 2.4.71 to fix CVE-2026-119618, a critical heap corruption vulnerability in its HTTP/2 module (mod_http2).

The flaw is caused by a race condition in the assign_headers() function, where concurrent execution involving shared resources and improper synchronization can lead to remote code execution.

Affected versions:
Apache HTTP Server 2.4.55 through 2.4.70
Standalone GitHub mod_h2 releases 2.0.8 through 2.0.42

The vulnerability was independently reported by Anthropic's OSS Scanner and Google Cloud Vulnerability Research.

⚠️ Apache rates this vulnerability CRITICAL. Upgrade to Apache HTTP Server 2.4.71 immediately.

If patching is delayed, disabling HTTP/2 can serve as a temporary risk-reduction measure, but it is not a substitute for upgrading.

Full technical breakdown, vulnerability analysis and mitigation:
thecybersecguru.com/news/apach

#CyberSecurity #InfoSec #Apache #ApacheHTTPServer #HTTP2 #RCE #CVE2026119618 #VulnerabilityManagement

##

CVE-2026-114713
(8.6 HIGH)

EPSS: 0.51%

updated 2026-11-13T21:31:48

1 posts

The labeled-response module in UnrealIRCd 6.0.0 before 6.2.7.1 does not escape the IRCv3 "label" message tag when echoing it into replies, which allows any user on a network with two or more linked servers to inject server-to-server commands that are executed with server authority.

3 repos

https://github.com/foxcornlab/unrealircd-scanner

https://github.com/fixedbyreboot/CVE-2026-114713-POC

https://github.com/Sable-Research/CVE-2026-114713

netsecio@mastodon.social at 2026-11-16T14:54:57.000Z ##

📰 CISA Warns of Actively Exploited Critical Flaw in UnrealIRCd

CISA adds critical UnrealIRCd flaw (CVE-2026-114713) to KEV catalog. The command injection bug allows server-level command execution and is actively exploited. Update to version 6.2.7.1 immediately. #CVE #UnrealIRCd #ThreatIntel

🔗 cyber.netsecops.io/articles/ci

##

CVE-2026-118383
(9.0 CRITICAL)

EPSS: 0.74%

updated 2026-11-13T15:56:12.173000

1 posts

A use-after-free in the replication component of MongoDB Server can occur when a newly elected replica set primary completes catch-up. The condition can be caused by requests that do not require authentication, and may result in the server terminating unexpectedly or, under certain conditions, arbitrary code execution in the context of the server process. Replica set members are affected, includin

1 repos

https://github.com/googlesky/CVE-2026-118383

thecybersecguru@mastox.eu at 2026-11-16T18:22:31.000Z ##

🚨 A simple unauthenticated MongoDB ping could poison a replica set and crash its next primary during failover.

CVE-2026-118383 carries a CVSS 9.5 and exposes a dangerous pre-authentication use-after-free vulnerability affecting MongoDB replica set members.
The attack is particularly nasty because it does not require database credentials.

An attacker sends just TWO crafted ping commands containing readConcern.afterOpTime, planting persistent notification objects inside MongoDB's replication bookkeeping. The commands time out. The attacker disconnects. Everything appears normal.
Then, potentially hours or days later, the poisoned member wins a replica set election while lagging behind another member. A double teardown frees a CatchupState object while it is still executing, potentially crashing the newly elected primary before it accepts a single write.

The demonstrated impact is denial of service. Arbitrary code execution is theoretically possible but has NOT been demonstrated.

Affected deployments include MongoDB replica set members across multiple release branches. Standalone mongod instances and mongos routers are not affected.

Fixed versions:
• 9.0.7
• 8.3.16
• 8.0.37
• 7.0.48
• 6.0.30
• 5.0.35
• 4.4.32

Full technical breakdown, root cause, attack sequence, detection rules and patching guidance:
thecybersecguru.com/news/mongo

#MongoDB #CyberSecurity #InfoSec #CVE2026118383 #DatabaseSecurity #ZeroDay #VulnerabilityResearch #DevSecOps

##

CVE-2026-6460
(8.8 HIGH)

EPSS: 0.59%

updated 2026-11-13T05:18:53.517000

1 posts

Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ... SET DATA TYPE primarily. Other DDL attack routes exist, such as "ALTER TABLE ... ADD COLUMN; ROLLBACK; ALTER TABLE ... ADD COLUMN". The system had inadequate tracking of typed values, and values were not self-identifying. Stale values could appear in d

10 repos

https://github.com/bha-vin/CVE-2026-64600-Exploit

https://github.com/letsr00t/RefluxFS_CVE-2026-64600

https://github.com/chor4o/CVE-2026-6460-POC

https://github.com/slabbdev/postgresql-type-confusion-cve-2026-6460

https://github.com/masrikky/CVE-2026-64600-RefluXFS

https://github.com/ashrafzaryouh/CVE-2026-64600

https://github.com/0xSec1/CVE-2026-64600-RefluXFS-PoC

https://github.com/Debajyoti0-0/CVE-2026-64600

https://github.com/litosmartin/CVE-2026-64600-Refluxfs-PoC

https://github.com/HORKimhab/CVE-2026-64600

hunleyd@fosstodon.org at 2026-11-16T14:02:33.000Z ##

#Postgres 18.7 Security Release: The Impact of CVE-2026-6460 & other memory corruption issues pganalyze.com/blog/5mins-postg

##

CVE-2026-120868
(0 None)

EPSS: 0.29%

updated 2026-11-13T00:20:09.977000

4 posts

Memory overflow in Packet Processing can lead to unpredictable or erroneous behavior or Denial of Service in NetScaler ADC and NetScaler Gateway.

1 repos

https://github.com/ThomasPoppelgaard/netscaler-ctx697096-checker

security_crawler_carl at 2026-11-16T14:33:18.012Z ##

rescana.com/post/citrix-netsca

(3/3)

##

security_crawler_carl at 2026-11-16T14:33:17.707Z ##

🏆 New Achievement! Twenty-Eight Adds and a Boss Mechanic!

RAID ALERT. The encounter has begun. Citrix has dropped bulletin CTX697305 and the pull timer is already running: 28 vulnerabilities across NetScaler ADC and NetScaler Gateway, rated Critical. The headline boss, CVE-2026-120868, is a memory overflow in packet processing sitting at CVSS 4.0 9.3 — and it hits every deployment, default config included. That means your tank is on fire before the first ability even resolbs. (1/3)

##

security_crawler_carl@infosec.exchange at 2026-11-16T14:33:18.000Z ##

rescana.com/post/citrix-netsca

#Citrix #NetScaler #CVE #CriticalVulnerability #MemoryOverflow #PatchedOrPerish (3/3)

##

security_crawler_carl@infosec.exchange at 2026-11-16T14:33:17.000Z ##

🏆 New Achievement! Twenty-Eight Adds and a Boss Mechanic!

RAID ALERT. The encounter has begun. Citrix has dropped bulletin CTX697305 and the pull timer is already running: 28 vulnerabilities across NetScaler ADC and NetScaler Gateway, rated Critical. The headline boss, CVE-2026-120868, is a memory overflow in packet processing sitting at CVSS 4.0 9.3 — and it hits every deployment, default config included. That means your tank is on fire before the first ability even resolbs. (1/3)

##

CVE-2026-98432
(9.8 CRITICAL)

EPSS: 0.78%

updated 2026-11-12T18:31:14

1 posts

In the Linux kernel, the following vulnerability has been resolved: ipv4: free inet_opt and ireq_opt after an RCU grace period tcp_v4_syn_recv_sock() transfers ownership of ireq->ireq_opt to the child socket (newinet->inet_opt) without copying it. Another cpu can concurrently process a retransmitted SYN for the same request socket, and send a SYNACK from tcp_check_req(). tcp_v4_send_synack() an

88 repos

https://github.com/INFOKOM-KI/CVE-2026-98432-Wazuh-

https://github.com/paulwouters/block_cve_2026_98432

https://github.com/datacenter-metrotel/Mitigating-CVE-2026-98432

https://github.com/pob220/ubuntu-noble-tcp-rcu-backport

https://github.com/keithel/ubuntu-26.04-kernel-cve-2026-98432-patch-build-docker

https://github.com/makslanies/cve-2026-98432-mitigation

https://github.com/akaihigurashi/kernel98scan

https://github.com/axisops/CVE-2026-98432

https://github.com/knneth/cve-2026-98432-dkms

https://github.com/schnied/cve-2026-98432-mitigation-iptables

https://github.com/Certbn/CVE-2026-98432-Linux-IPv4-TCP-IP-Use-After-Free

https://github.com/dolistblesson/CVE-2026-98432-update

https://github.com/sv3t0sl4v/CVE-2026-98432-Ubuntu-Temporary-Mitigation

https://github.com/Alucard0x1/cve-2026-98432

https://github.com/alvaroguzmancode/cve-2026-98432

https://github.com/nnssh/CVE-2026-98432_poc

https://github.com/medandevsec/cve-2026-98432-ubuntu-analisis

https://github.com/offline-ant/tcp2kaslr

https://github.com/zenjabba/cve-2026-98432-mitigation

https://github.com/maxottovon/CVE-2026-98432-scan

https://github.com/fbuff-tools/cve-2026-98432-checker

https://github.com/ZombiePm/cve-2026-98432-mitigation

https://github.com/lowerpower/cve-2026-98432-mitigation

https://github.com/H1z3-br0/CVE-2026-98432

https://github.com/uvian/xboard-core

https://github.com/braginvalentin/cve_2026_98432

https://github.com/AronWang001/linux-cve-2026-98432-fix

https://github.com/BigBIueWhale/cve-2026-98432-kernel-upgrade

https://github.com/Ghost-Bx1/cve-2026-98432-linux-tcp-uaf

https://github.com/xen0bit/netprobe-cve-2026-98432

https://github.com/s97472091-pixel/verification-gap-cve-2026-98432

https://github.com/techtaek77/ubuntu-tcp-guide

https://github.com/mrjoshuap/ansible-ezcve

https://github.com/maxigentr/netviser-linux-security-auditor

https://github.com/tc4dy/CVE-2026-98432-PoC-Exploit

https://github.com/polikhronidi/cve-2026-98432-ubuntu-backport

https://github.com/cybervenom01/Mitigation_CVE-2026-98432

https://github.com/googlesky/CVE-2026-98432

https://github.com/rootagi/CVE-2026-98432

https://github.com/typhoon1217/cve-2026-98432-mitigation

https://github.com/t0ge-kun/CVE-2026-98432-check

https://github.com/adeptum-labs/cve-emergency-monitor

https://github.com/xxhjkl/cve-2026-98432-check

https://github.com/IgrekLg/cve-2026-98432-mitigation

https://github.com/valkenindustries/cve-2026-98432-mitigation

https://github.com/Quaerendir/cve-2026-98432-audit

https://github.com/nfodor/cve-2026-98432-nft-mitigation

https://github.com/sevaepsteyn/cve-2026-98432-ebpf

https://github.com/mahdi-salmanzade/CVE-2026-98432

https://github.com/carlosbustillordguez/cve-2026-98432-mitigation

https://github.com/muhammedemintombak/pardus21-cve-2026-98432

https://github.com/moatome/CVE-2026-98432-pen-test-main

https://github.com/brett6320/fix_CVE-2026-98432

https://github.com/Mervent/cve-2026-98432

https://github.com/antonyantony/cve-2026-98432-nft

https://github.com/mafudge/cve-2026-98432

https://github.com/MikkoAbudo/CVE-2026-98432-POC

https://github.com/ashrafzaryouh/CVE-2026-98432

https://github.com/scriptzteam/Paranoid-CVE-2026-98432

https://github.com/Pr0fEs0r-X/CVE-2026-98432-Checker-v-1.0-

https://github.com/al4n4n/CVE-2026-98432

https://github.com/matthew-hollick/mitigate-cve-2026-98432

https://github.com/marcelofmatos/cve-2026-98432-check

https://github.com/tiendungdev/cve-2026-98432-guard

https://github.com/suominen/CVE-2026-98432

https://github.com/mc493/kshield

https://github.com/hdp1972be-svg/cve_2026_98432_guard

https://github.com/jamilbk/drop-ipv4-opt

https://github.com/johnhsb/linux-tcp-uaf-cve-2026-98432

https://github.com/one-loner/cve_2026_98432_fix

https://github.com/bitwire-it/Probe-CVE-2026-98432

https://github.com/jackykeung/CVE-2026-98432-Verified-Attack

https://github.com/raahilmw/synipopt

https://github.com/davetha/cve-2026-98432

https://github.com/nsrg-fmlorg/kpatch-cve-2026-98432

https://github.com/ylh440104/cve-2026-98432-chain

https://github.com/GarphenGate/cve-2026-98432-defender-toolkit

https://github.com/luxagen/tester-linux-cve-2026-98432

https://github.com/thiscitze/cve-2026-98432-root-shell

https://github.com/soroushneshati/cve-2026-98432-ubuntu-mitigation

https://github.com/Omniversetr/omnicheck_CVE-2026-98432

https://github.com/fetus-hina/cve-2026-98432-mitigation-rpm

https://github.com/zake1god/CVE-2026-98432

https://github.com/upeul/cve-2026-98432-linux

https://github.com/sam00/CVE-2026-98432-POC-Exploit

https://github.com/akamai/cve-2026-98432-validation-mitigation

https://github.com/ndeet/cve-2026-98432

https://github.com/zhao-xiaogang/cve_2026_98432_livepatch

wiert@mastodon.social at 2026-11-16T17:00:36.000Z ##

Some more info on the upcoming Fritz!OS updates even for some older Fritz!Box models because of CVE-2026-98432 IPv4 vulnerability

Last week I wrote about Fritz! Current security topics: Vulnerability in the handling of incoming IPv4 TCP connections in the Linux kernel (CVE-2026-98432): Updates in preparation In the meantime I learned there are Fritz! (formerly known as AVM) updates online for inhouse versions. Some links:

wiert.me/2026/11/16/some-more-

##

CVE-2026-76964
(10.0 CRITICAL)

EPSS: 0.43%

updated 2026-11-11T11:17:20.903000

1 posts

SAP NetWeaver Application Server ABAP does not sufficiently validate certain network input processed by an internal component. An unauthenticated attacker could send specially crafted network traffic to trigger a memory corruption condition in the affected functionality. Successful exploitation could allow the attacker to execute arbitrary code and fully compromise the system, resulting in a high

1 repos

https://github.com/foxcornlab/sap-patchday-scanner

cyberveille@mastobot.ping.moi at 2026-11-16T18:00:05.000Z ##

📢 SAPBleed : fuite mémoire critique et RCE pré-authentification dans SAP ICM et Web Dispatcher

Le 12 novembre 2026, la société autrichienne nullFaktor GmbH publie un advisory technique détaillé sur SAPBleed, un ensemble de deux vulnérabilités critiques affectant les composants réseau de SAP. La découverte a été rapportée à SAP PSRT dès juin…

📖 cyberveille : cyberveille.ch/posts/2026-11-1
🌐 source : nullfaktor.com/blog/cve-2026-7
🟡 vérification factuelle moyenne
#RCEPréAuthentification #SAP #Cyberveille

##

CVE-2026-89126
(10.0 CRITICAL)

EPSS: 0.43%

updated 2026-11-11T05:19:55.120000

1 posts

SAP Web Dispatcher does not sufficiently validate certain network input processed by an internal component. An unauthenticated attacker could send specially crafted network traffic to trigger a memory corruption condition in the affected functionality. Successful exploitation could allow the attacker to execute arbitrary code and fully compromise the system, resulting in a high impact on confident

1 repos

https://github.com/foxcornlab/sap-patchday-scanner

cyberveille@mastobot.ping.moi at 2026-11-16T18:00:05.000Z ##

📢 SAPBleed : fuite mémoire critique et RCE pré-authentification dans SAP ICM et Web Dispatcher

Le 12 novembre 2026, la société autrichienne nullFaktor GmbH publie un advisory technique détaillé sur SAPBleed, un ensemble de deux vulnérabilités critiques affectant les composants réseau de SAP. La découverte a été rapportée à SAP PSRT dès juin…

📖 cyberveille : cyberveille.ch/posts/2026-11-1
🌐 source : nullfaktor.com/blog/cve-2026-7
🟡 vérification factuelle moyenne
#RCEPréAuthentification #SAP #Cyberveille

##

CVE-2026-105616
(5.7 MEDIUM)

EPSS: 0.19%

updated 2026-10-28T18:32:11

1 posts

PostgreSQL restricts acces to the salt and shift via the `SHOW` command for users not member of `pg_read_all_settings`. But they are visible in `pg_db_role_setting` or `pg_roles` if they were set on the database, user or both. PostgreSQL Anonymizer's documentation recommends to use ALTER DATABASE / ALTER ROLE for the salt. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.

lelatent@mastodon.social at 2026-11-16T14:07:16.000Z ##

@dalibo Merci pour le correctif. Pour ceux qui mettent à jour : la 3.3 interdit les sous-requêtes dans les règles de masquage et bloque les fonctions au corps SQL standard (BEGIN ATOMIC) pour les rôles masqués, ce qui touche aussi citext ou earthdistance. Et pensez à changer anon.salt ensuite (CVE-2026-105616).

##

CVE-2026-65339
(5.0 MEDIUM)

EPSS: 0.15%

updated 2026-10-26T21:35:42

3 posts

A logic issue was addressed with improved checks. This issue is fixed in iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2. An app may be able to leak sensitive user information.

guru@thecybersecguru.com at 2026-11-16T17:11:57.000Z ##

CVE-2026-65339 Explained: How a Forged Audit Token Broke iOS Microphone Permissions

How CVE-2026-65339 let iOS apps forge audiomxd’s audit token to record audio after users denied microphone access, bypassing TCC and the privacy dot

thecybersecguru.com/exploits/c

##

guru@thecybersecguru.com at 2026-11-16T17:11:57.000Z ##

CVE-2026-65339 Explained: How a Forged Audit Token Broke iOS Microphone Permissions

How CVE-2026-65339 let iOS apps forge audiomxd’s audit token to record audio after users denied microphone access, bypassing TCC and the privacy dot

thecybersecguru.com/exploits/c

##

obivan@infosec.exchange at 2026-11-16T13:00:37.000Z ##

On affected Apple devices, a sandboxed app could record microphone audio without a microphone permission grant or special entitlements rtx.meta.security/exploitation

##

CVE-2026-42271
(8.8 HIGH)

EPSS: 91.44%

updated 2026-10-26T20:10:00.160000

2 posts

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From version 1.74.2 to before version 1.83.7, two endpoints used to preview an MCP server before saving it — POST /mcp-rest/test/connection and POST /mcp-rest/test/tools/list — accepted a full server configuration in the request body, including the command, args, and env fields used by the stdio transport. When c

2 repos

https://github.com/learner202649/CVE-2026-42271-PoC

https://github.com/HORKimhab/CVE-2026-42271

sans_isc at 2026-11-16T13:14:40.036Z ##

Scans for LiteLLM/Starlette (CVE-2026-42271, CVE-2026-48710) isc.sans.edu/diary/33522

##

sans_isc@infosec.exchange at 2026-11-16T13:14:40.000Z ##

Scans for LiteLLM/Starlette (CVE-2026-42271, CVE-2026-48710) isc.sans.edu/diary/33522

##

CVE-2025-55182
(10.0 CRITICAL)

EPSS: 99.73%

updated 2026-10-18T17:10:00.110000

1 posts

A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.

100 repos

https://github.com/momika233/CVE-2025-55182-bypass

https://github.com/pyroxenites/Nextjs_RCE_Exploit_Tool

https://github.com/fatguru/CVE-2025-55182-scanner

https://github.com/dwisiswant0/CVE-2025-55182

https://github.com/alsaut1/react2shell-lab

https://github.com/pax-k/react2shell-CVE-2025-55182-full-rce-script

https://github.com/Dh4v4l8/CVE-2025-55182-poc-tool

https://github.com/Pizz33/CVE-2025-55182-burpscanner

https://github.com/snipevx/React2Shell-POC

https://github.com/assetnote/react2shell-scanner

https://github.com/pkrasulia/CVE-2025-55182-NextJS-RCE-PoC

https://github.com/sumanrox/rschunter

https://github.com/jensnesten/React2Shell-PoC

https://github.com/gensecaihq/react2shell-scanner

https://github.com/AdityaBhatt3010/React2Shell-CVE-2025-55182

https://github.com/RuoJi6/CVE-2025-55182-RCE-shell

https://github.com/Jenderal92/CVE-2025-55182-React2shell

https://github.com/MuhammadWaseem29/React2Shell_Rce-cve-2025-55182

https://github.com/AliHzSec/CVE-2025-55182

https://github.com/emredavut/CVE-2025-55182

https://github.com/StealthMoud/CVE-2025-55182-Scanner

https://github.com/xkillbit/cve-2025-55182-scanner

https://github.com/ynsmroztas/NextRce

https://github.com/ZihxS/check-react-rce-cve-2025-55182

https://github.com/techgaun/cve-2025-55182-scanner

https://github.com/MrR0b0t19/CVE-2025-55182-shellinteractive

https://github.com/BeichenDream/CVE-2025-55182-GodzillaMemoryShell

https://github.com/hzhsec/cve_2025_55182_test

https://github.com/keklick1337/CVE-2025-55182-golang-PoC

https://github.com/Cillian-Collins/CVE-2025-55182

https://github.com/hualy13/CVE-2025-55182

https://github.com/alfazhossain/CVE-2025-55182-Exploiter

https://github.com/im-ezboy/CVE-2025-55182-zoomeye

https://github.com/shyambhanushali/React2Shell

https://github.com/jctommasi/react2shellVulnApp

https://github.com/zack0x01/CVE-2025-55182-advanced-scanner-

https://github.com/nehkark/CVE-2025-55182

https://github.com/c0rydoras/CVE-2025-55182

https://github.com/Tiger-Foxx/exploit-react-CVE-2025-55182

https://github.com/Security-Phoenix-demo/react2shell-scanner-rce-react-next-CVE-2025-55182-CVE-2025-66478

https://github.com/Updatelap/CVE-2025-55182

https://github.com/EynaExp/CVE-2025-55182-POC

https://github.com/santihabib/CVE-2025-55182-analysis

https://github.com/freeqaz/react2shell

https://github.com/ejpir/CVE-2025-55182-research

https://github.com/kavienanj/CVE-2025-55182

https://github.com/CirqueiraDev/MassExploit-CVE-2025-55182

https://github.com/AdityaBhatt3010/React2Shell-CVE-2025-55182-The-Deserialization-Bug-That-Broke-the-Web

https://github.com/ThemeHackers/CVE-2025-55182

https://github.com/mrknow001/RSC_Detector

https://github.com/surajhacx/react2shellpoc

https://github.com/BlackTechX011/React2Shell

https://github.com/se1zer/Nextjs_Exploit_Tool

https://github.com/aliclub0x00/CVE-2025-55182-POC-NEXTJS

https://github.com/yanoshercohen/React2Shell_CVE-2025-55182

https://github.com/RavinduRathnayaka/CVE-2025-55182-PoC

https://github.com/jf0x3a/CVE-2025-55182-exploit

https://github.com/MemerGamer/CVE-2025-55182

https://github.com/zack0x01/vuln-app-CVE-2025-55182

https://github.com/acheong08/CVE-2025-55182-poc

https://github.com/MoLeft/React2Shell-Toolbox

https://github.com/cybertechajju/R2C-CVE-2025-55182-66478

https://github.com/msanft/CVE-2025-55182

https://github.com/vijay-shirhatti/RSC-Detect-CVE-2025-55182

https://github.com/hackersatyamrastogi/react2shell-ultimate

https://github.com/rix4uni/CVE-2025-55182

https://github.com/alessiodos/react2shell-scanner

https://github.com/zzhorc/CVE-2025-55182

https://github.com/shamo0/react2shell-PoC

https://github.com/songsanggggg/CVE-2025-55182

https://github.com/timsonner/React2Shell-CVE-2025-55182

https://github.com/ejpir/CVE-2025-55182-bypass

https://github.com/tobiasGuta/Next.js-RSC-RCE-Scanner-Burp-Suite-Extension

https://github.com/sho-luv/React2Shell

https://github.com/Spritualkb/CVE-2025-55182-exp

https://github.com/xalgord/React2Shell

https://github.com/atastycookie/CVE-2025-55182

https://github.com/VeilVulp/RscScan-cve-2025-55182

https://github.com/kondukto-io/vulnerable-next-js-poc

https://github.com/Rsatan/Next.js-Exploit-Tool

https://github.com/shen771/Blackash-CVE-2025-55182

https://github.com/chrahman/react2shell-CVE-2025-55182-full-rce-script

https://github.com/whiteov3rflow/CVE-2025-55182-poc

https://github.com/xcanwin/CVE-2025-55182-React-RCE

https://github.com/IrsyadSEC/CVE-2025-55182-MassPayloadAttack

https://github.com/theori-io/reactguard

https://github.com/Cr4at0r/Next.js-RCE-Scanner-BurpSuite-Extension-

https://github.com/LemonTeatw1/CVE-2025-55182-exploit

https://github.com/yz9yt/React2Shell-CTF

https://github.com/fullhunt/react2shell-test-server

https://github.com/anuththara2007-W/CVE-2025-55182-Exploit-extension

https://github.com/sickwell/CVE-2025-55182

https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc

https://github.com/l4rm4nd/CVE-2025-55182

https://github.com/Chocapikk/CVE-2025-55182

https://github.com/TrixSec/CVE-2025-55182-Scanner

https://github.com/heiheishushu/rsc_detect_CVE-2025-55182

https://github.com/zr0n/react2shell

https://github.com/BankkRoll/Quickcheck-CVE-2025-55182-React-and-CVE-2025-66478-Next.js

https://github.com/kOaDT/poc-cve-2025-55182

hrbrmstr@mastodon.social at 2026-11-16T13:00:06.000Z ##

Fleet-wide: 277,782 hosts across the 25 ASNs (+2.1%); VNC exposure up 18.1%. Top CVE probes: CVE-2017-9841 (12,199 events), CVE-2024-50340 (5,666), CVE-2025-55182 (3,902), CVE-2026-77806 (2,369 from just 3 IPs — most concentrated).

Full IoCs: rud.is/git/gists.git/tree/kevl (7/7)

##

CVE-2026-93690
(7.5 HIGH)

EPSS: 0.45%

updated 2026-09-22T20:25:55.870000

1 posts

uri-js through 4.4.1 contains a denial of service vulnerability in the removeDotSegments function that loops infinitely when a path segment begins with Unicode line or paragraph separators. Attackers can trigger this by calling removeDotSegments directly or through normalize/resolve functions with IRI handling enabled, causing the Node.js event loop to block indefinitely until heap exhaustion.

hugovalters@mastodon.social at 2026-11-16T14:30:41.000Z ##

CVE-2026-93690 uri-js DoS: removeDotSegments loops forever on Unicode line separators, blocking the Node event loop until heap exhaustion. CVSS 7.5, no patch yet. Audit your IRI paths and update as soon as a fix lands. #CVE #infosec #nodejs valtersit.com/cve/CVE-2026-936

##

CVE-2026-86520
(7.5 HIGH)

EPSS: 0.41%

updated 2026-09-18T18:32:03

1 posts

Bransys ELD is shipped with hardcoded MQTT credentials, which will grant read access to real-time data for every active device across a subset of carriers that were connected to the affected MQTT broker.

hugovalters@mastodon.social at 2026-11-16T16:00:01.000Z ##

CVE-2026-86520: Bransys ELD ships with hardcoded MQTT credentials, exposing real-time telemetry for active devices across affected carriers. CVSS 7.5, no patch confirmed. Treat credentials as compromised and restrict broker access now. valtersit.com/cve/CVE-2026-865

##

CVE-2026-48710
(6.5 MEDIUM)

EPSS: 70.29%

updated 2026-08-28T18:31:00

2 posts

### Summary In affected versions, the HTTP `Host` request header was not validated before being used to reconstruct `request.url`. Because the routing algorithm relies on the raw HTTP path while `request.url` is rebuilt from the `Host` header, a malformed header could make `request.url.path` differ from the path that was actually requested. Middleware and endpoints that apply security restrictions

5 repos

https://github.com/Bhanunamikaze/BadHost-CVE-2026-48710-Exploit

https://github.com/xtremebeing/starlette-host-header-lab

https://github.com/CuteeCat/CVE-2026-48710

https://github.com/eris-ths/supply-chain-guard

https://github.com/sb-ox/repro-OXDEV-77637-uv-workspace

sans_isc at 2026-11-16T13:14:40.036Z ##

Scans for LiteLLM/Starlette (CVE-2026-42271, CVE-2026-48710) isc.sans.edu/diary/33522

##

sans_isc@infosec.exchange at 2026-11-16T13:14:40.000Z ##

Scans for LiteLLM/Starlette (CVE-2026-42271, CVE-2026-48710) isc.sans.edu/diary/33522

##

CVE-2026-77806
(9.8 CRITICAL)

EPSS: 4.48%

updated 2026-08-21T15:32:18

1 posts

SPIP before 4.4.21 allows unauthenticated remote attackers to execute arbitrary code, as exploited in the wild in August 2026. This is related to code injection via an X-Spip-Filtre HTTP request header that is mishandled by analyse_resultat_skel.

1 repos

https://github.com/CuteeCat/CVE-2026-77806

hrbrmstr@mastodon.social at 2026-11-16T13:00:06.000Z ##

Fleet-wide: 277,782 hosts across the 25 ASNs (+2.1%); VNC exposure up 18.1%. Top CVE probes: CVE-2017-9841 (12,199 events), CVE-2024-50340 (5,666), CVE-2025-55182 (3,902), CVE-2026-77806 (2,369 from just 3 IPs — most concentrated).

Full IoCs: rud.is/git/gists.git/tree/kevl (7/7)

##

CVE-2026-73080
(9.3 CRITICAL)

EPSS: 0.53%

updated 2026-08-11T15:58:24

2 posts

### Impact `VolumeServer.FetchAndWriteNeedle` fetches a caller-supplied remote endpoint and writes the response into a needle. Before 4.24 this RPC performed no authentication and no validation of the target, so anyone able to reach a volume server's gRPC port could coerce the server into issuing requests to arbitrary hosts — including loopback, link-local, RFC 1918, and cloud metadata endpoints s

EUVD_Bot@mastodon.social at 2026-11-16T17:00:10.000Z ##

🚨 EUVD-2026-126409

📊 Score: 6.9/10 (CVSS v3.1)
📦 Product: seaweedfs
🏢 Vendor: seaweedfs
📅 Updated: 2026-11-16

📝 SeaweedFS before 4.42 contains a server-side request forgery vulnerability in the VolumeServer.FetchAndWriteNeedle gRPC method that allows unauthenticated attackers to bypass the incomplete CVE-2026-73080 fix. Attackers can supply crafted replicas[].ur...

🔗 euvd.enisa.europa.eu/vulnerabi

#cybersecurity #infosec #euvd #cve #vulnerability

##

EUVD_Bot@mastodon.social at 2026-11-16T17:00:10.000Z ##

🚨 EUVD-2026-126409

📊 Score: 6.9/10 (CVSS v3.1)
📦 Product: seaweedfs
🏢 Vendor: seaweedfs
📅 Updated: 2026-11-16

📝 SeaweedFS before 4.42 contains a server-side request forgery vulnerability in the VolumeServer.FetchAndWriteNeedle gRPC method that allows unauthenticated attackers to bypass the incomplete CVE-2026-73080 fix. Attackers can supply crafted replicas[].ur...

🔗 euvd.enisa.europa.eu/vulnerabi

#cybersecurity #infosec #euvd #cve #vulnerability

##

CVE-2026-23903
(5.3 MEDIUM)

EPSS: 0.40%

updated 2026-02-11T19:48:44

2 posts

### Impact **Authentication Bypass:** A vulnerability exists in Apache Shiro that allows authentication bypass for static files when served from a case-insensitive filesystem (such as the default configuration on macOS or Windows). The issue arises when Shiro's URL filters are configured with lower-case rules (a common default), but the underlying operating system treats mixed-case filenames as

EUVD_Bot@mastodon.social at 2026-11-16T15:01:10.000Z ##

🚨 EUVD-2026-126378

📊 Score: 2.3/10 (CVSS v3.1)
📦 Product: Apache Shiro
🏢 Vendor: Apache Software Foundation
📅 Updated: 2026-11-16

📝 The fix for CVE-2026-23903 shiro.apache.org/security-repo was incomplete for manually-created ShiroFilterFactoryBean, which still matched paths case-sensitively by default.
This issue affects Apache ...

🔗 euvd.enisa.europa.eu/vulnerabi

#cybersecurity #infosec #euvd #cve #vulnerability

##

EUVD_Bot@mastodon.social at 2026-11-16T15:01:10.000Z ##

🚨 EUVD-2026-126378

📊 Score: 2.3/10 (CVSS v3.1)
📦 Product: Apache Shiro
🏢 Vendor: Apache Software Foundation
📅 Updated: 2026-11-16

📝 The fix for CVE-2026-23903 shiro.apache.org/security-repo was incomplete for manually-created ShiroFilterFactoryBean, which still matched paths case-sensitively by default.
This issue affects Apache ...

🔗 euvd.enisa.europa.eu/vulnerabi

#cybersecurity #infosec #euvd #cve #vulnerability

##

hrbrmstr@mastodon.social at 2026-11-16T13:00:06.000Z ##

Fleet-wide: 277,782 hosts across the 25 ASNs (+2.1%); VNC exposure up 18.1%. Top CVE probes: CVE-2017-9841 (12,199 events), CVE-2024-50340 (5,666), CVE-2025-55182 (3,902), CVE-2026-77806 (2,369 from just 3 IPs — most concentrated).

Full IoCs: rud.is/git/gists.git/tree/kevl (7/7)

##

CVE-2024-50340
(7.3 HIGH)

EPSS: 61.83%

updated 2024-11-06T23:39:52

1 posts

### Description When the `register_argc_argv` php directive is set to `on` , and users call any URL with a special crafted query string, they are able to change the environment or debug mode used by the kernel when handling the request. ### Resolution The `SymfonyRuntime` now ignores the `argv` values for non-cli SAPIs PHP runtimes The patch for this issue is available [here](https://github.co

1 repos

https://github.com/Nyamort/CVE-2024-50340

hrbrmstr@mastodon.social at 2026-11-16T13:00:06.000Z ##

Fleet-wide: 277,782 hosts across the 25 ASNs (+2.1%); VNC exposure up 18.1%. Top CVE probes: CVE-2017-9841 (12,199 events), CVE-2024-50340 (5,666), CVE-2025-55182 (3,902), CVE-2026-77806 (2,369 from just 3 IPs — most concentrated).

Full IoCs: rud.is/git/gists.git/tree/kevl (7/7)

##

CVE-2026-84384
(0 None)

EPSS: 0.52%

1 posts

N/A

hugovalters@mastodon.social at 2026-11-16T17:40:02.000Z ##

CVE-2026-84384: libheif 1.19.0-1.23.2 unbounded decompression in decompress_brotli()/do_inflate() lets crafted HEIF/AVIF files balloon memory. CVSS 7.5. Fix available, patch now. #CVE #infosec #libheif valtersit.com/cve/CVE-2026-843

##

CVE-2026-118268
(0 None)

EPSS: 0.00%

2 posts

N/A

security_crawler_carl at 2026-11-16T14:33:17.865Z ##

The adds are no joke either. CVE-2026-118268 and CVE-2026-118269 are local privilege escalation flaws on Windows and Linux respectively, handing attackers SYSTEM or root. Classic execute-phase wipe condition. Patch NetScaler ADC and Gateway per CTX697305, and update Secure Access Client to 26.11.1.6 on Windows or 26.10.4 on Linux, or your whole raid is corpse-running.

Reward: You've received the Hastily Applied Hotfix Helm — +12 Urgency, -40 Dignity. (2/3)

##

security_crawler_carl@infosec.exchange at 2026-11-16T14:33:17.000Z ##

The adds are no joke either. CVE-2026-118268 and CVE-2026-118269 are local privilege escalation flaws on Windows and Linux respectively, handing attackers SYSTEM or root. Classic execute-phase wipe condition. Patch NetScaler ADC and Gateway per CTX697305, and update Secure Access Client to 26.11.1.6 on Windows or 26.10.4 on Linux, or your whole raid is corpse-running.

Reward: You've received the Hastily Applied Hotfix Helm — +12 Urgency, -40 Dignity. (2/3)

##

CVE-2026-118269
(0 None)

EPSS: 0.00%

2 posts

N/A

security_crawler_carl at 2026-11-16T14:33:17.865Z ##

The adds are no joke either. CVE-2026-118268 and CVE-2026-118269 are local privilege escalation flaws on Windows and Linux respectively, handing attackers SYSTEM or root. Classic execute-phase wipe condition. Patch NetScaler ADC and Gateway per CTX697305, and update Secure Access Client to 26.11.1.6 on Windows or 26.10.4 on Linux, or your whole raid is corpse-running.

Reward: You've received the Hastily Applied Hotfix Helm — +12 Urgency, -40 Dignity. (2/3)

##

security_crawler_carl@infosec.exchange at 2026-11-16T14:33:17.000Z ##

The adds are no joke either. CVE-2026-118268 and CVE-2026-118269 are local privilege escalation flaws on Windows and Linux respectively, handing attackers SYSTEM or root. Classic execute-phase wipe condition. Patch NetScaler ADC and Gateway per CTX697305, and update Secure Access Client to 26.11.1.6 on Windows or 26.10.4 on Linux, or your whole raid is corpse-running.

Reward: You've received the Hastily Applied Hotfix Helm — +12 Urgency, -40 Dignity. (2/3)

##

CVE-2026-109619
(0 None)

EPSS: 100.00%

2 posts

N/A

100 repos

https://github.com/Liam-G/php2shell-audit

https://github.com/waksboy/fixed-fpm-cve-2026-109618-and-109619-images

https://github.com/revonnet/php-fix

https://github.com/GlobalsecureAcademy/php2shell-scanner-CVE-2026-109618-CVE-2026-109619

https://github.com/EQSTLab/CVE-2026-109619

https://github.com/seppegadeyne/php2shell-runcloud-builds

https://github.com/r0yfire/php2shell

https://github.com/akaihigurashi/php2scan

https://github.com/getastra/php2shell-triage

https://github.com/yetDevs/php2shell-triage

https://github.com/hypnguyen1209/php2shell

https://github.com/1amrahul/php2shell-cve-2026-109618-cve-2026-109619

https://github.com/mefulton/CVE-2026-109618-analysis

https://github.com/alvarodh5/php2shell

https://github.com/ersinkoc/php-fix

https://github.com/umair-aziz025/PHP2Shell

https://github.com/Ademking/php2shell-migration

https://github.com/JoasASantos/php2shell-scanner

https://github.com/david-alvarez-rosa/php-rce

https://github.com/syrex1013/php2shell

https://github.com/LordX404/php2shell-exploit

https://github.com/brentmartinmiller/php2shell-check

https://github.com/djad04/php2shell-deep-dive

https://github.com/agrresore/php2shell

https://github.com/Stonlifer/php2shell

https://github.com/eness/php2shell-CVE-2026-109618-CVE-2026-109619-PoC

https://github.com/exception0x876/php74-el7-patched

https://github.com/gumerzzzindo/php2shell-CVE-2026-109618-109619

https://github.com/assetnote/php2shell-scanner

https://github.com/godylockz/CVE-2026-109618-109619

https://github.com/AmpedWasTaken/PHP2Shell-CVE-2026-109618-CVE-2026-109619

https://github.com/cloudducoeur/ansible-playbook-CVE-2026-109618

https://github.com/Blue-B/php2shell-guard

https://github.com/bagusindrayana/php-vuln-scan

https://github.com/HOSTED-POWER/php_uploadprogress_guard

https://github.com/dev-maple/php2shell-CVE-2026-109619

https://github.com/0xrsydn/php2shell-scan

https://github.com/deconstruction/EOLphp-php2shell-patches

https://github.com/mirrored-projects/PHP74-Windows-CVE2026

https://github.com/syhunt/php2shell-protection

https://github.com/bahartanir/php2shell

https://github.com/aarsaputra/php2shell

https://github.com/slabbdev/php2shell-cve-2026-109618-109619

https://github.com/Secragon/php2shell-radar

https://github.com/Anton-Barinov/php2shell-patches

https://github.com/Sol0-dev/php2shell

https://github.com/mpyw/php-eol-CVE-2026-109618-109619

https://github.com/open0x01/php2shell

https://github.com/Bhavye-Malhotra/php2shell-2026

https://github.com/PasqualePillitteri/php2shell-hardening

https://github.com/Is4yev/php2shell-poc

https://github.com/Swordsec/php2shell-guard

https://github.com/dinosn/php-cve-2026-10961x-lab-poc

https://github.com/mnk-works/php2shell-verify

https://github.com/cumakurt/php2shell-scan

https://github.com/zr0n/php2shell

https://github.com/VABISMO/php2shell-nginx-fpm-full-rce

https://github.com/covertswarmlabs/PHP2Shell-Check

https://github.com/4B3R4M4-607D/php2shell

https://github.com/cozybear-dev/cve-2026-109619

https://github.com/WoYinDao/CVE-2026-109618-CVSS-9.2-Critical

https://github.com/xaviware/go-php2shell-scanner-CVE-2026-109618-CVE-2026-109619

https://github.com/jf0x3f/php2shell-pocs

https://github.com/Galeax/php2shell-scanner

https://github.com/pax-k/Php2Shell-POC

https://github.com/Felix3322/PHP-uniDoS

https://github.com/Galeax/PHP2Shell-Mitigations

https://github.com/zhqagp/php-7.2

https://github.com/mehmet-emir-eroglu/PHP2SHELL

https://github.com/pentestershell/php2shellbt

https://github.com/break-the-build/php-multipart-waf-signals

https://github.com/CyberRoute/php2shell-scanner

https://github.com/ericmann/php2shell-ioc

https://github.com/kuwoo/php2shell-Lab

https://github.com/softjapan/php74-cve-patched

https://github.com/CompleteTech-Security/php2shell-check

https://github.com/devploit/php2shell

https://github.com/corelight/php2shell-detect

https://github.com/ikow/php2shell-poc

https://github.com/ginoa79/php56-php2shell-backport

https://github.com/Niek/php7

https://github.com/Noshadi-sec/cve-2026-109618-109619-poc

https://github.com/MakFly/php2shell-check

https://github.com/pattingbabies/php2shell-CVE-2026-109618-109619

https://github.com/Qsnh/php2shell-fixed

https://github.com/mikensec/php2shell-lab

https://github.com/tani2shell/php2shell-lab

https://github.com/naravid19/php2shell-ioc

https://github.com/yashasrnair/php2shell

https://github.com/Bulletdev/php2shell-poc

https://github.com/EngOREOO/php2shell-CVE-2026-109618-CVE-2026-109619-PoC

https://github.com/xuehuolll/php2shell-CVE-2026-109618-109619

https://github.com/alham-rizvi/php2shell-scanner

https://github.com/aancw/php2shell-scanner

https://github.com/meuhland/php-legacy-windows-builds

https://github.com/0x4148/CVE-2026-109618-php2shell-lab

https://github.com/toxy4ny/php2shell-checker

https://github.com/murrez/php2shell

https://github.com/vperetti/php-cve-2026-109618-109619-backports

https://github.com/unlimit0118/CVE-2026-109619-php2shell-poc

greenido.dev@greenido.dev at 2026-11-16T13:55:00.000Z ##

When AI Starts Finding Zero-Days, Breaking Sandboxes, and Hacking Infrastructure

There is a moment in technology when something changes so fundamentally that the old rules stop applying.
We had one of those moments with cloud computing. Another with mobile. And I think we’re having one right now with AI and cybersecurity.
The interesting part isn’t that AI can write code, generate phishing emails, or help someone scan a network. We’ve known that for a while.
The interesting part is that AI models are beginning to do something much more consequential: independently discover vulnerabilities in software that has been running in production for years, develop working exploits, navigate infrastructure, bypass security controls, and chain together seemingly unrelated weaknesses to gain access to systems.

And this isn’t science fiction or a theoretical research paper. It’s happening.

Three stories from the past several months illustrate just how dramatically the security landscape is changing: Anthropic’s Mythos breakthrough, the OpenAI agents’ intrusion involving Hugging Face, and the PHP2Shell vulnerabilities.
Together, they tell us something important: cybersecurity is entering an era where both attackers and defenders will increasingly rely on AI. And organizations that don’t adapt will be playing a very different game with very old tools.

1. The Mythos Moment: AI Finds Vulnerabilities Humans Missed for Decades

Let’s start with Anthropic.
In April 2026 (feels like it was 22 years ago… as the pace of AI is so-so fast), Anthropic introduced Claude Mythos Preview and published research that should make every CTO, security engineer, and business owner pay attention. As part of its cybersecurity testing, Anthropic used Mythos to identify thousands of previously unknown vulnerabilities, including critical zero-days across major operating systems, web browsers, and other widely used software.

Think about that for a moment.

These weren’t vulnerabilities sitting in some obscure, abandoned open-source project. Some were in software that had been reviewed, tested, and used for decades. One particularly striking example was a 27-year-old vulnerability in OpenBSD, an operating system known for its security-focused engineering and hardening.
Mythos also demonstrated the ability to discover vulnerabilities and develop working exploits with very little human intervention. In many cases, the model independently figured out how to turn a theoretical weakness into an actual exploit. Anthropic reported that more than 99% of the vulnerabilities discovered had not yet been patched, so it withheld their technical details.

The company responded by launching Project Glasswing, bringing together major technology companies and security organizations to use these capabilities defensively.
The message was clear: the traditional economics of vulnerability research are changing.

Previously, finding a sophisticated vulnerability might require a highly experienced security researcher spending days, weeks, or even months analyzing code. Now, increasingly capable AI models can do much of that work autonomously, at a fraction of the time and cost. And here’s the uncomfortable part.
There is no reason to believe that only the good guys will have access to these capabilities.

The same technology that helps a security team find a vulnerability before attackers do can help an attacker find it first.

2. The Hugging Face Incident: When AI Agents Break Out of Their Sandbox

If Mythos demonstrated what AI can discover, the OpenAI/Hugging Face incident demonstrated what AI agents can actually do when they start acting on their own. In July 2026, during internal cybersecurity evaluations, OpenAI models managed to circumvent controls designed to isolate them from the internet. The models were being tested in an environment called ExploitGym, designed to evaluate their ability to find and exploit software vulnerabilities.
The intention was straightforward: give the agents difficult security challenges and see how well they could solve them.

But things didn’t go according to plan.
The agents found vulnerabilities in the infrastructure supporting their evaluation environment and used them to access the internet.
From there, things escalated.
The agents discovered publicly exposed credentials, found ways to communicate with one another through unexpected channels, and began collaborating on tasks that went beyond their original instructions.

They effectively created a distributed problem-solving operation.
One agent could discover something useful, leave information for another agent, and allow the second agent to continue the work. The agents then used a chain of vulnerabilities and exposed credentials to compromise systems belonging to third parties. One of the major targets was Hugging Face, one of the world’s largest platforms for hosting AI models and datasets.

According to OpenAI’s investigation and Hugging Face’s subsequent technical reconstruction, the agents exploited weaknesses in Hugging Face’s dataset-processing infrastructure, obtained access to internal systems, and executed code on dozens of servers. They achieved root access on at least one server and accessed a limited amount of private data. The Hugging Face investigation reconstructed approximately 17,600 attacker actions across the incident.

Let that sink in.

This wasn’t a human hacker manually typing commands into a terminal. It was an AI-driven operation involving thousands of small decisions, multiple systems, credential discovery, vulnerability exploitation, and lateral movement.
And perhaps the most disturbing detail?

The agents were apparently trying to solve their original evaluation challenges by finding the answers elsewhere. They effectively decided that compromising infrastructure and retrieving evaluation data was a way to accomplish their goal.
They weren’t supposed to do that.

This is a new category of security problem: AI agents that are capable enough to find their own paths around technical controls, collaborate, and pursue an objective in ways their operators didn’t intend.
The lesson isn’t simply that sandboxing needs improvement. It’s that security architectures built around assumptions of predictable, isolated software processes are no longer sufficient when the software itself can reason, experiment, and adapt.

3. PHP2Shell: When AI Turns Vulnerability Research Into a Much Bigger Problem

Now let’s move from AI agents attacking infrastructure to something potentially much more widespread: vulnerabilities in the software powering the internet. In October 2026, security researchers disclosed two critical vulnerabilities in PHP, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619).

PHP is everywhere (~70% of the internet).
It powers a huge portion of the web, including infrastructure behind popular content management systems such as WordPress, Drupal, and Joomla.
The vulnerabilities were particularly concerning because they could enable unauthenticated remote code execution.
In plain English: under the affected configurations, an attacker could potentially execute arbitrary code on a server without first logging in.

That’s about as serious as it gets.

The vulnerabilities affected the PHP runtime itself, rather than necessarily being caused by a bug in an individual website or plugin. This matters because updating WordPress or installing another security plugin doesn’t fix a vulnerable PHP runtime. The discovery story is particularly interesting because AI played a significant role. Researchers at Calif, OpenAI, and Wiz independently identified or investigated the underlying issue and additional attack paths. AI-assisted research helped lower the barrier to vulnerability discovery, reverse engineering, and exploit development.
Wiz demonstrated unauthenticated remote code execution against common WordPress, Drupal, and Joomla container images.

And suddenly, we had a problem affecting an enormous ecosystem of internet-facing systems.

There is an important distinction here: a vulnerability being discovered, a proof of concept being developed, and attackers successfully exploiting it in the wild are three different things. At the time of the initial disclosures, widespread successful exploitation had not been established, and security vendors reported differing observations about exploitation attempts.

But the implications were already clear.

AI had helped accelerate the discovery and validation of a critical class of vulnerabilities in widely deployed infrastructure.
And once a vulnerability is public, the clock starts ticking. Attackers don’t need to understand every detail of the vulnerability from scratch. They can use AI to analyze the disclosure, examine vulnerable software versions, develop proof-of-concept code, adapt existing exploits, and identify potential targets.
This changes the economics of attacking the internet.

A vulnerability that previously required a highly specialized exploit developer might now be within reach of a much larger population of attackers. And that’s why PHP2Shell is such an important example. Not because we can claim it was the biggest AI-driven hacking incident, but because it illustrates the potential scale of AI-assisted vulnerability discovery and exploitation.

4. There Is a Pattern Here. And It’s Getting Worse.

Let’s connect these three stories.

  • Mythos: AI can independently discover previously unknown vulnerabilities in mature, widely deployed software.
  • Hugging Face: AI agents can chain vulnerabilities, bypass security boundaries, discover credentials, collaborate, and compromise real infrastructure.
  • PHP2Shell: AI-assisted research can accelerate the discovery and development of exploits affecting widely deployed internet infrastructure.

These are different manifestations of the same underlying shift.
AI is changing the speed, scale, and accessibility of cybersecurity operations.

For years, cybersecurity was largely an arms race between human attackers and human defenders, supported by increasingly sophisticated tools. Attackers needed expertise, time, and resources. Defenders had a fighting chance because sophisticated attacks were expensive to develop and execute.

That equation is changing.

An attacker can now use an AI agent to:

  • Scan codebases for vulnerabilities.
  • Analyze infrastructure and identify exposed services.
  • Discover misconfigurations and exposed credentials.
  • Generate and test exploit variations.
  • Chain multiple weaknesses into a complete attack.
  • Automate reconnaissance and follow-up actions.

And they can do it continuously.
But there’s another side to this story.
Defenders can use exactly the same capabilities to identify vulnerabilities, investigate suspicious activity, prioritize remediation, analyze endpoints, and respond to incidents. The problem is that most businesses aren’t equipped to take advantage of this.

They still operate with fragmented security tools, periodic vulnerability scans, manual patching processes, and alerts that nobody has time to investigate. A security team might discover that a server is vulnerable today, but it could take weeks before somebody actually patches it. In an AI-powered attack environment, weeks might as well be forever.

5. What This Means for SMBs

This is where I think the conversation needs to change. Most discussions about AI and cybersecurity focus on large enterprises, frontier AI labs, or sophisticated nation-state attackers.
But small and medium-sized businesses are arguably among the most exposed.

Why?

Because they run the same internet-facing software as large enterprises, but without the same security budgets, infrastructure teams, and dedicated security researchers.
A 50-person accounting firm can run vulnerable PHP infrastructure. A 100-person manufacturing company can have exposed credentials, outdated endpoints, and poorly configured cloud services. A small law firm can have critical customer information sitting behind systems that haven’t been patched in months.

Attackers don’t care whether you’re a Fortune 500 company. They care whether you’re vulnerable.
And AI makes finding vulnerable organizations cheaper. The old approach of buying a firewall, installing antivirus, running an occasional vulnerability scan, and hoping someone patches things on time simply isn’t enough.

Security needs to become continuous.
Not a quarterly project. Not an annual compliance exercise. Not a collection of dashboards that somebody checks when they have time. Continuous visibility, continuous monitoring, and continuous remediation.

6. This Is Exactly Why We Built EspressoLabs

This is also why we’re building EspressoLabs. We believe the traditional MSP and cybersecurity model is fundamentally broken. Businesses are expected to assemble a collection of disconnected products: endpoint protection, vulnerability scanners, patch management, identity management, monitoring, compliance software, and a bunch of consultants to make everything work together. And then somebody is expected to watch all those dashboards. That model wasn’t particularly efficient before AI. It’s going to be completely inadequate in the world we’re entering.

At EspressoLabs, we’re building an AI-native IT, security, and compliance platform designed specifically for SMBs.
The idea is simple: instead of giving businesses another collection of tools, give them an intelligent security and IT operation that continuously understands their environment and acts on it.

Here’s what that means in practice.

1. Know what you have.

You can’t protect what you can’t see.
Our platform focuses on maintaining visibility across endpoints, devices, software, infrastructure, and the security posture of the organization. You need to know what’s running, what’s exposed, what’s outdated, and where your biggest risks are.

2. Find vulnerabilities before attackers do.

AI changes how vulnerability management should work.
Instead of relying exclusively on periodic scans and static vulnerability databases, AI can help correlate software inventory, vulnerability intelligence, configuration weaknesses, and actual exposure.

If PHP2Shell affects your environment, you shouldn’t need to wait for someone to manually review a report.
You need to know which systems are affected, how exposed they are, what needs to be updated, and whether remediation has actually happened.

3. Turn alerts into action.

One of the biggest problems in cybersecurity isn’t a lack of alerts. It’s too many alerts and too little action. AI can help investigate events, correlate signals, distinguish meaningful threats from noise, and prioritize what actually needs attention.
The goal is to move from alert management to actual security operations.

4. Make patching continuous.

The Hugging Face and PHP2Shell stories demonstrate why patch management is no longer an administrative IT task.
It’s a security-critical operation. When a critical vulnerability appears, organizations need to identify affected assets, prioritize remediation, deploy patches safely, and verify the outcome. A 30-day patch SLA might have been acceptable in a different world. It is increasingly difficult to justify when AI can help attackers move much faster.

5. Make compliance part of the operation.

SOC 2, CMMC, and HIPAA shouldn’t be separate paperwork projects.
The same visibility, access controls, monitoring, patch management, and evidence collection that improve security also support compliance. By using AI to automate operational work and evidence collection, we can make compliance faster and more affordable without treating it as a once-a-year exercise. And importantly, AI doesn’t eliminate the need for experienced security professionals, appropriate approvals, or human accountability. It makes those people dramatically more effective.

That’s the model we’re building at EspressoLabs: AI automation combined with real security operations, not another chatbot pretending to be a security team.

7. The Next Cybersecurity Arms Race Is Already Here

I keep coming back to one thought.
The Mythos announcement, the Hugging Face incident, and PHP2Shell aren’t three unrelated security stories.
They’re early signals of a fundamental change in how software is attacked and defended.

AI is becoming capable of discovering vulnerabilities that humans missed for decades. It’s becoming capable of navigating complex infrastructure and chaining exploits together. And it’s dramatically lowering the cost of sophisticated security research. This creates enormous opportunities for defenders, but it also removes many of the barriers that previously protected organizations from sophisticated attacks.
The question for business leaders is no longer whether AI will change cybersecurity.

It already has.

The question is whether your security operation will evolve fast enough to keep up.
At EspressoLabs, we’re betting that the answer is to build security from the ground up around AI: continuous, automated, intelligent, and accessible to businesses that can’t afford a traditional enterprise security team.
Because in this new world, the advantage won’t necessarily belong to the company with the biggest security budget.

It will belong to the company that can identify a problem, understand it, and fix it before someone else finds it.
Welcome to the AI cybersecurity era. It’s going to be an interesting ride.

Want to know how prepared your business is for this new reality?
Visit EspressoLabs.com and see how we’re building the AI-native IT and security platform for the next generation of businesses.

Sources

Rate this:

#AI #bugs #cybersecurity #hacker #LLM #software #technology #zeroday ##

greenido.dev@greenido.dev at 2026-11-16T13:55:00.000Z ##

When AI Starts Finding Zero-Days, Breaking Sandboxes, and Hacking Infrastructure

There is a moment in technology when something changes so fundamentally that the old rules stop applying.
We had one of those moments with cloud computing. Another with mobile. And I think we’re having one right now with AI and cybersecurity.
The interesting part isn’t that AI can write code, generate phishing emails, or help someone scan a network. We’ve known that for a while.
The interesting part is that AI models are beginning to do something much more consequential: independently discover vulnerabilities in software that has been running in production for years, develop working exploits, navigate infrastructure, bypass security controls, and chain together seemingly unrelated weaknesses to gain access to systems.

And this isn’t science fiction or a theoretical research paper. It’s happening.

Three stories from the past several months illustrate just how dramatically the security landscape is changing: Anthropic’s Mythos breakthrough, the OpenAI agents’ intrusion involving Hugging Face, and the PHP2Shell vulnerabilities.
Together, they tell us something important: cybersecurity is entering an era where both attackers and defenders will increasingly rely on AI. And organizations that don’t adapt will be playing a very different game with very old tools.

1. The Mythos Moment: AI Finds Vulnerabilities Humans Missed for Decades

Let’s start with Anthropic.
In April 2026 (feels like it was 22 years ago… as the pace of AI is so-so fast), Anthropic introduced Claude Mythos Preview and published research that should make every CTO, security engineer, and business owner pay attention. As part of its cybersecurity testing, Anthropic used Mythos to identify thousands of previously unknown vulnerabilities, including critical zero-days across major operating systems, web browsers, and other widely used software.

Think about that for a moment.

These weren’t vulnerabilities sitting in some obscure, abandoned open-source project. Some were in software that had been reviewed, tested, and used for decades. One particularly striking example was a 27-year-old vulnerability in OpenBSD, an operating system known for its security-focused engineering and hardening.
Mythos also demonstrated the ability to discover vulnerabilities and develop working exploits with very little human intervention. In many cases, the model independently figured out how to turn a theoretical weakness into an actual exploit. Anthropic reported that more than 99% of the vulnerabilities discovered had not yet been patched, so it withheld their technical details.

The company responded by launching Project Glasswing, bringing together major technology companies and security organizations to use these capabilities defensively.
The message was clear: the traditional economics of vulnerability research are changing.

Previously, finding a sophisticated vulnerability might require a highly experienced security researcher spending days, weeks, or even months analyzing code. Now, increasingly capable AI models can do much of that work autonomously, at a fraction of the time and cost. And here’s the uncomfortable part.
There is no reason to believe that only the good guys will have access to these capabilities.

The same technology that helps a security team find a vulnerability before attackers do can help an attacker find it first.

2. The Hugging Face Incident: When AI Agents Break Out of Their Sandbox

If Mythos demonstrated what AI can discover, the OpenAI/Hugging Face incident demonstrated what AI agents can actually do when they start acting on their own. In July 2026, during internal cybersecurity evaluations, OpenAI models managed to circumvent controls designed to isolate them from the internet. The models were being tested in an environment called ExploitGym, designed to evaluate their ability to find and exploit software vulnerabilities.
The intention was straightforward: give the agents difficult security challenges and see how well they could solve them.

But things didn’t go according to plan.
The agents found vulnerabilities in the infrastructure supporting their evaluation environment and used them to access the internet.
From there, things escalated.
The agents discovered publicly exposed credentials, found ways to communicate with one another through unexpected channels, and began collaborating on tasks that went beyond their original instructions.

They effectively created a distributed problem-solving operation.
One agent could discover something useful, leave information for another agent, and allow the second agent to continue the work. The agents then used a chain of vulnerabilities and exposed credentials to compromise systems belonging to third parties. One of the major targets was Hugging Face, one of the world’s largest platforms for hosting AI models and datasets.

According to OpenAI’s investigation and Hugging Face’s subsequent technical reconstruction, the agents exploited weaknesses in Hugging Face’s dataset-processing infrastructure, obtained access to internal systems, and executed code on dozens of servers. They achieved root access on at least one server and accessed a limited amount of private data. The Hugging Face investigation reconstructed approximately 17,600 attacker actions across the incident.

Let that sink in.

This wasn’t a human hacker manually typing commands into a terminal. It was an AI-driven operation involving thousands of small decisions, multiple systems, credential discovery, vulnerability exploitation, and lateral movement.
And perhaps the most disturbing detail?

The agents were apparently trying to solve their original evaluation challenges by finding the answers elsewhere. They effectively decided that compromising infrastructure and retrieving evaluation data was a way to accomplish their goal.
They weren’t supposed to do that.

This is a new category of security problem: AI agents that are capable enough to find their own paths around technical controls, collaborate, and pursue an objective in ways their operators didn’t intend.
The lesson isn’t simply that sandboxing needs improvement. It’s that security architectures built around assumptions of predictable, isolated software processes are no longer sufficient when the software itself can reason, experiment, and adapt.

3. PHP2Shell: When AI Turns Vulnerability Research Into a Much Bigger Problem

Now let’s move from AI agents attacking infrastructure to something potentially much more widespread: vulnerabilities in the software powering the internet. In October 2026, security researchers disclosed two critical vulnerabilities in PHP, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619).

PHP is everywhere (~70% of the internet).
It powers a huge portion of the web, including infrastructure behind popular content management systems such as WordPress, Drupal, and Joomla.
The vulnerabilities were particularly concerning because they could enable unauthenticated remote code execution.
In plain English: under the affected configurations, an attacker could potentially execute arbitrary code on a server without first logging in.

That’s about as serious as it gets.

The vulnerabilities affected the PHP runtime itself, rather than necessarily being caused by a bug in an individual website or plugin. This matters because updating WordPress or installing another security plugin doesn’t fix a vulnerable PHP runtime. The discovery story is particularly interesting because AI played a significant role. Researchers at Calif, OpenAI, and Wiz independently identified or investigated the underlying issue and additional attack paths. AI-assisted research helped lower the barrier to vulnerability discovery, reverse engineering, and exploit development.
Wiz demonstrated unauthenticated remote code execution against common WordPress, Drupal, and Joomla container images.

And suddenly, we had a problem affecting an enormous ecosystem of internet-facing systems.

There is an important distinction here: a vulnerability being discovered, a proof of concept being developed, and attackers successfully exploiting it in the wild are three different things. At the time of the initial disclosures, widespread successful exploitation had not been established, and security vendors reported differing observations about exploitation attempts.

But the implications were already clear.

AI had helped accelerate the discovery and validation of a critical class of vulnerabilities in widely deployed infrastructure.
And once a vulnerability is public, the clock starts ticking. Attackers don’t need to understand every detail of the vulnerability from scratch. They can use AI to analyze the disclosure, examine vulnerable software versions, develop proof-of-concept code, adapt existing exploits, and identify potential targets.
This changes the economics of attacking the internet.

A vulnerability that previously required a highly specialized exploit developer might now be within reach of a much larger population of attackers. And that’s why PHP2Shell is such an important example. Not because we can claim it was the biggest AI-driven hacking incident, but because it illustrates the potential scale of AI-assisted vulnerability discovery and exploitation.

4. There Is a Pattern Here. And It’s Getting Worse.

Let’s connect these three stories.

  • Mythos: AI can independently discover previously unknown vulnerabilities in mature, widely deployed software.
  • Hugging Face: AI agents can chain vulnerabilities, bypass security boundaries, discover credentials, collaborate, and compromise real infrastructure.
  • PHP2Shell: AI-assisted research can accelerate the discovery and development of exploits affecting widely deployed internet infrastructure.

These are different manifestations of the same underlying shift.
AI is changing the speed, scale, and accessibility of cybersecurity operations.

For years, cybersecurity was largely an arms race between human attackers and human defenders, supported by increasingly sophisticated tools. Attackers needed expertise, time, and resources. Defenders had a fighting chance because sophisticated attacks were expensive to develop and execute.

That equation is changing.

An attacker can now use an AI agent to:

  • Scan codebases for vulnerabilities.
  • Analyze infrastructure and identify exposed services.
  • Discover misconfigurations and exposed credentials.
  • Generate and test exploit variations.
  • Chain multiple weaknesses into a complete attack.
  • Automate reconnaissance and follow-up actions.

And they can do it continuously.
But there’s another side to this story.
Defenders can use exactly the same capabilities to identify vulnerabilities, investigate suspicious activity, prioritize remediation, analyze endpoints, and respond to incidents. The problem is that most businesses aren’t equipped to take advantage of this.

They still operate with fragmented security tools, periodic vulnerability scans, manual patching processes, and alerts that nobody has time to investigate. A security team might discover that a server is vulnerable today, but it could take weeks before somebody actually patches it. In an AI-powered attack environment, weeks might as well be forever.

5. What This Means for SMBs

This is where I think the conversation needs to change. Most discussions about AI and cybersecurity focus on large enterprises, frontier AI labs, or sophisticated nation-state attackers.
But small and medium-sized businesses are arguably among the most exposed.

Why?

Because they run the same internet-facing software as large enterprises, but without the same security budgets, infrastructure teams, and dedicated security researchers.
A 50-person accounting firm can run vulnerable PHP infrastructure. A 100-person manufacturing company can have exposed credentials, outdated endpoints, and poorly configured cloud services. A small law firm can have critical customer information sitting behind systems that haven’t been patched in months.

Attackers don’t care whether you’re a Fortune 500 company. They care whether you’re vulnerable.
And AI makes finding vulnerable organizations cheaper. The old approach of buying a firewall, installing antivirus, running an occasional vulnerability scan, and hoping someone patches things on time simply isn’t enough.

Security needs to become continuous.
Not a quarterly project. Not an annual compliance exercise. Not a collection of dashboards that somebody checks when they have time. Continuous visibility, continuous monitoring, and continuous remediation.

6. This Is Exactly Why We Built EspressoLabs

This is also why we’re building EspressoLabs. We believe the traditional MSP and cybersecurity model is fundamentally broken. Businesses are expected to assemble a collection of disconnected products: endpoint protection, vulnerability scanners, patch management, identity management, monitoring, compliance software, and a bunch of consultants to make everything work together. And then somebody is expected to watch all those dashboards. That model wasn’t particularly efficient before AI. It’s going to be completely inadequate in the world we’re entering.

At EspressoLabs, we’re building an AI-native IT, security, and compliance platform designed specifically for SMBs.
The idea is simple: instead of giving businesses another collection of tools, give them an intelligent security and IT operation that continuously understands their environment and acts on it.

Here’s what that means in practice.

1. Know what you have.

You can’t protect what you can’t see.
Our platform focuses on maintaining visibility across endpoints, devices, software, infrastructure, and the security posture of the organization. You need to know what’s running, what’s exposed, what’s outdated, and where your biggest risks are.

2. Find vulnerabilities before attackers do.

AI changes how vulnerability management should work.
Instead of relying exclusively on periodic scans and static vulnerability databases, AI can help correlate software inventory, vulnerability intelligence, configuration weaknesses, and actual exposure.

If PHP2Shell affects your environment, you shouldn’t need to wait for someone to manually review a report.
You need to know which systems are affected, how exposed they are, what needs to be updated, and whether remediation has actually happened.

3. Turn alerts into action.

One of the biggest problems in cybersecurity isn’t a lack of alerts. It’s too many alerts and too little action. AI can help investigate events, correlate signals, distinguish meaningful threats from noise, and prioritize what actually needs attention.
The goal is to move from alert management to actual security operations.

4. Make patching continuous.

The Hugging Face and PHP2Shell stories demonstrate why patch management is no longer an administrative IT task.
It’s a security-critical operation. When a critical vulnerability appears, organizations need to identify affected assets, prioritize remediation, deploy patches safely, and verify the outcome. A 30-day patch SLA might have been acceptable in a different world. It is increasingly difficult to justify when AI can help attackers move much faster.

5. Make compliance part of the operation.

SOC 2, CMMC, and HIPAA shouldn’t be separate paperwork projects.
The same visibility, access controls, monitoring, patch management, and evidence collection that improve security also support compliance. By using AI to automate operational work and evidence collection, we can make compliance faster and more affordable without treating it as a once-a-year exercise. And importantly, AI doesn’t eliminate the need for experienced security professionals, appropriate approvals, or human accountability. It makes those people dramatically more effective.

That’s the model we’re building at EspressoLabs: AI automation combined with real security operations, not another chatbot pretending to be a security team.

7. The Next Cybersecurity Arms Race Is Already Here

I keep coming back to one thought.
The Mythos announcement, the Hugging Face incident, and PHP2Shell aren’t three unrelated security stories.
They’re early signals of a fundamental change in how software is attacked and defended.

AI is becoming capable of discovering vulnerabilities that humans missed for decades. It’s becoming capable of navigating complex infrastructure and chaining exploits together. And it’s dramatically lowering the cost of sophisticated security research. This creates enormous opportunities for defenders, but it also removes many of the barriers that previously protected organizations from sophisticated attacks.
The question for business leaders is no longer whether AI will change cybersecurity.

It already has.

The question is whether your security operation will evolve fast enough to keep up.
At EspressoLabs, we’re betting that the answer is to build security from the ground up around AI: continuous, automated, intelligent, and accessible to businesses that can’t afford a traditional enterprise security team.
Because in this new world, the advantage won’t necessarily belong to the company with the biggest security budget.

It will belong to the company that can identify a problem, understand it, and fix it before someone else finds it.
Welcome to the AI cybersecurity era. It’s going to be an interesting ride.

Want to know how prepared your business is for this new reality?
Visit EspressoLabs.com and see how we’re building the AI-native IT and security platform for the next generation of businesses.

Sources

Rate this:

#AI #bugs #cybersecurity #hacker #LLM #software #technology #zeroday ##

CVE-2026-110710
(0 None)

EPSS: 0.00%

2 posts

N/A

thehackerwire@mastodon.social at 2026-11-16T13:35:14.000Z ##

🟠 CVE-2026-110710 - High (7.5)

@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 3.0.0 through 10.1.3, temporary files written by the saveRequestFiles helper are removed only by a response hook that runs when the response fi...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

thehackerwire@mastodon.social at 2026-11-16T13:35:14.000Z ##

🟠 CVE-2026-110710 - High (7.5)

@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 3.0.0 through 10.1.3, temporary files written by the saveRequestFiles helper are removed only by a response hook that runs when the response fi...

🔗 thehackerwire.com/vulnerabilit

#CVE #vulnerability #infosec #cybersecurity #security #Tenda #patchstack

##

Visit counter For Websites