Vulnerability intelligence

Updated 24 minutes ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

1000100

Current score

It's getting all log4shell

  1. 1

    CVE-2026-109618 Published Oct 21, 2026

    Hype score

    100

    critical 9.2

    PHPPHP2Shell

    CVE-2026-109618 is a remote code execution (RCE) vulnerability affecting the PHP core. The flaw reportedly impacts a wide range of PHP versions, specifically versions 5, 6, 7, and 8. While specific technical details have been withheld by researchers to prevent exploitation, cybersecurity firm watchTowr confirmed the vulnerability's validity and successfully reproduced it in their testing environment. The vulnerability was originally under embargo for a coordinated disclosure on October 22, 2026, but details of the flaw leaked early on October 20, 2026, via a post on Hacker News. In response to the premature leak, the PHP security team accelerated its release timeline, scheduling emergency security updates for October 21, 2026, to address the issue.

  2. 2

    CVE-2026-109619 Published Oct 21, 2026

    Hype score

    100

    critical 9.2

    PHPPHP2Shell

    CVE-2026-109619 is a remote code execution (RCE) vulnerability affecting the PHP scripting language. Security researchers and early reports indicate that the flaw impacts PHP versions 5, 6, 7, and 8. While specific technical details regarding the vulnerability's mechanics have not been publicly disclosed, successful exploitation could allow an unauthenticated remote attacker to execute arbitrary code with the privileges of the underlying PHP process. The vulnerability was originally scheduled for coordinated disclosure under embargo on October 22, 2026. However, after information about the flaw leaked online on October 20, the PHP security team accelerated its timeline, scheduling a security release for October 21, 2026, at 14:00 UTC. Security organizations and researchers have advised administrators to prepare to apply the upcoming patches as soon as they are released.

  3. 3

    CVE-2026-96656 Published Sep 23, 2026

    Hype score

    22

    high 8.6

    Exploit known

    Plex Media Server

    CVE-2026-96656 is an external control of file name or path vulnerability affecting Plex Media Server versions prior to 1.43.3.10861. The flaw allows an administrator—or an attacker who has obtained administrative privileges—to write arbitrary files, specifically ELF shared objects (`.so` files), to an attacker-chosen path within the server's Codecs directory. Because Plex Media Server loads and executes all `.so` files in this directory at startup without verifying signatures, execute bits, or symbols, this arbitrary file write leads to code execution. Additionally, the vulnerability involves the `TranscoderH264Options` preference, which is appended verbatim to the x264 option string during transcoding. This vulnerability serves as the final stage of a four-part exploit chain known as "Plex2Shell," which also includes CVE-2026-96652, CVE-2026-96654, and CVE-2026-96655. When combined, these flaws allow unauthenticated remote code execution on exposed Plex Media Server instances. Following the public release of a proof-of-concept exploit in October 2026, threat actors began actively targeting unpatched servers in the wild to deploy payloads such as XMRig cryptocurrency miners and reverse proxy software. Plex addressed the issue in an update released in August 2026.

See more

Known exploited

Sourced from CISA's Known Exploited Vulnerability (KEV) catalog.

  1. CVE-2026-96656 Published Sep 23, 2026

    Hype score

    22

    high 8.6

    Exploit known

    Plex Media Server

    CVE-2026-96656 is an external control of file name or path vulnerability affecting Plex Media Server versions prior to 1.43.3.10861. The flaw allows an administrator—or an attacker who has obtained administrative privileges—to write arbitrary files, specifically ELF shared objects (`.so` files), to an attacker-chosen path within the server's Codecs directory. Because Plex Media Server loads and executes all `.so` files in this directory at startup without verifying signatures, execute bits, or symbols, this arbitrary file write leads to code execution. Additionally, the vulnerability involves the `TranscoderH264Options` preference, which is appended verbatim to the x264 option string during transcoding. This vulnerability serves as the final stage of a four-part exploit chain known as "Plex2Shell," which also includes CVE-2026-96652, CVE-2026-96654, and CVE-2026-96655. When combined, these flaws allow unauthenticated remote code execution on exposed Plex Media Server instances. Following the public release of a proof-of-concept exploit in October 2026, threat actors began actively targeting unpatched servers in the wild to deploy payloads such as XMRig cryptocurrency miners and reverse proxy software. Plex addressed the issue in an update released in August 2026.

  2. CVE-2026-96655 Published Sep 23, 2026

    Hype score

    22

    medium 5.3

    Exploit known

    Plex Media Server

    CVE-2026-96655 is a server-side request forgery (SSRF) vulnerability affecting Plex Media Server versions prior to 1.43.3.10861. The flaw resides in the `/video/:/transcode/universal` path parameter, where it allows an authenticated user possessing the owner's token to request arbitrary internal or external network addresses. Discovered by security researcher Zach Main, the vulnerability was patched by Plex in August 2026. This vulnerability is a component of "Plex2Shell," a chain of four vulnerabilities that can be combined to achieve unauthenticated remote code execution on exposed Plex servers. Following the public release of technical details and proof-of-concept code in October 2026, attackers began actively exploiting this chain in the wild. Observed attacks have utilized the exploit chain to deploy cryptocurrency miners and residential proxy software on vulnerable systems.

  3. CVE-2026-96654 Published Sep 23, 2026

    Hype score

    22

    medium 6.9

    Exploit known

    Plex Media Server

    CVE-2026-96654 is a vulnerability affecting Plex Media Server versions prior to 1.43.3.10861. The flaw arises from the improper neutralization of URL values within the "searchOne" endpoint. This allows an attacker to call functions belonging to other plugins and supply custom parameters, enabling them to obtain the server owner's administrator token. This vulnerability is tracked as part of a chain of four security flaws collectively referred to as "Plex2Shell". When chained together, these flaws allow attackers to execute arbitrary code on vulnerable Plex Media Server instances without needing valid credentials. Following the public release of a proof-of-concept exploit, threat actors have actively targeted these vulnerabilities in the wild to deploy cryptocurrency miners and reverse proxy software. The issue was patched by Plex in August 2026.

See more

Insights

See more

Our Security Team's most recent CVE analysis

  1. CVE-2026-109619

    critical 9.2

    Link to CVE page

    Intruder Insights

    Updated Oct 21, 2026

    CVE-2026-109618 and CVE-2026-109619 are being collectively named "PHP2Shell". These weaknesses were due to be published as an advisory, but information was leaked early that's led to researchers and attackers getting a head start. The weaknesses have an RCE impact when exploitation is successful, and affect a wide range of in-support and out-of-support PHP versions. No patch has been announced for out-of-support versions, and no mitigations have been confirmed as being 100% effective.

    The current recommended solution is to inventory ALL usage of PHP across your network, and patch as soon as possible. Patches are only available for 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

    For inventory purposes, make sure to consider popular 3rd party products using PHP such as WordPress, Magento, MediaWiki, Drupal, etc. And frameworks for PHP development such as Laravel, CodeIgniter, and Symfony

    PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).

  2. CVE-2026-109618

    critical 9.2

    Link to CVE page

    Intruder Insights

    Updated Oct 21, 2026

    CVE-2026-109618 and CVE-2026-109619 are being collectively named "PHP2Shell". These weaknesses were due to be published as an advisory, but information was leaked early that's led to researchers and attackers getting a head start. The weaknesses have an RCE impact when exploitation is successful, and affect a wide range of in-support and out-of-support PHP versions. No patch has been announced for out-of-support versions, and no mitigations have been confirmed as being 100% effective.

    The current recommended solution is to inventory ALL usage of PHP across your network, and patch as soon as possible. Patches are only available for 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

    For inventory purposes, make sure to consider popular 3rd party products using PHP such as WordPress, Magento, MediaWiki, Drupal, etc. And frameworks for PHP development such as Laravel, CodeIgniter, and Symfony

    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 lead to remote code execution (RCE).

  3. Link to CVE page

    Intruder Insights

    Updated Sep 10, 2026

    This is a serious vulnerability affecting all supported WordPress versions. It can be exploited by any unauthenticated attacker, and a working proof of concept is available. However, to achieve remote code execution an attacker must trick a WordPress admin into opening a malicious link as part of a social engineering attack. This vulnerability is patched in WordPress 7.0.3 (released Aug 6, 2026).

    WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE vulnerability with conditions outside of the attackers control. This requires successful social engineering of and explicit interaction by the target victim. This issue affects all versions of WordPress. Version 7.0.3 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7. Discovered and responsibly disclosed by [the team at pwn.ai](https://pwn.ai/).