Vulnerability intelligence

Updated 40 minutes ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

380100

Current score

Tepid

  1. 1

    CVE-2026-109618 Published Oct 21, 2026

    Hype score

    38

    critical 9.2

    Exploit known

    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

    37

    critical 9.2

    Exploit known

    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-84496 Published Oct 26, 2026

    Hype score

    23

    medium 6.5

    macOS TahoemacOS Golden Gate

    CVE-2026-84496 is an out-of-bounds write vulnerability affecting the Apple File System (APFS) in macOS. The issue occurs when the operating system attempts to mount a maliciously crafted disk image. If triggered, this flaw can cause unexpected system termination or corrupt the system's kernel memory. The vulnerability was discovered and reported to Apple by a collaborative group of security researchers, including Maher Azzouzi, Jonathan Bar Or, and several others. Apple resolved the issue by implementing improved bounds checking to prevent unauthorized out-of-bounds writes. The security patch was released on October 26, 2026, and is included in the macOS Golden Gate 27.2 and macOS Tahoe 26.7.2 software updates.

See more

Known exploited

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

  1. CVE-2026-48356 Published Jul 14, 2026

    critical 9.3

    Exploit known

    PolyShellAdobe Commerce

    CVE-2026-48356 is an unrestricted file upload vulnerability affecting Adobe Commerce, Magento Open Source, Adobe Commerce B2B, and the Adobe I/O Events connector for Commerce. The flaw arises from insufficient validation of uploaded file types, allowing attackers to upload files without adequate restrictions on their extension or MIME classification. This enables attackers to place content on the system that a web server interprets as an executable script. Successful exploitation requires user interaction—such as a victim visiting a maliciously crafted URL or interacting with a compromised page—and can lead to arbitrary code execution in the context of the current user, potentially granting the attacker elevated access or control over the victim's session. Also known as "PolyShell," the vulnerability has been actively exploited in the wild, with activity traced back to at least July 2025. Security researchers have observed attackers leveraging the flaw to breach hundreds of e-commerce stores, injecting malicious loaders via Magento CMS blocks to fetch and execute attacker-controlled payloads. Due to this active exploitation, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-48356 to its Known Exploited Vulnerabilities (KEV) catalog in October 2026. Adobe addressed the issue in its July 2026 security updates (APSB26-73), and organizations are advised to apply the patches and inspect their systems for unauthorized file uploads.

  2. CVE-2026-111497 Published Oct 22, 2026

    critical 9.2

    Exploit known

    broccolinode2shellhttp2shellNode.js

    CVE-2026-111497 is a vulnerability affecting the Brotli decompression library integrated into Node.js (specifically within the 22.x, 24.x, and 26.x release lines) and other platforms like Envoy. The flaw is characterized as an out-of-bounds write memory error in the Brotli decoder. When a system decodes Brotli-compressed data, a bug in how the decoder unpacks the data allows it to write past the end of its allocated memory block. This memory corruption can be triggered when an application processes untrusted or malicious Brotli-compressed content, potentially allowing an attacker to leak memory or achieve remote code execution (RCE). To mitigate this issue, users are advised to update to patched versions of Node.js, which include 22.23.4, 24.22.1, and 26.12.1.

  3. CVE-2026-109619 Published Oct 21, 2026

    Hype score

    37

    critical 9.2

    Exploit known

    PHP2ShellPHP

    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.

See more

Insights

See more

Our Security Team's most recent CVE analysis

  1. CVE-2026-109619

    critical 9.2

    Exploit known

    Link to CVE page

    Intruder Insights

    Updated Oct 22, 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.

    CVE-2026-109619 in particular is RCE via stale global state. Request-owned state (including session and object data) can survive after the memory backing it has been freed. A later request handled by the same worker can then use that stale state before normal initialisation resets it.

    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

    Exploit known

    Link to CVE page

    Intruder Insights

    Updated Oct 22, 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.

    CVE-2026-109618 in particular is RCE via OOM corruption. PHP uses a jump to abort a request when it runs out of memory. If that abort fires while request data is only partially initialised — for example, while parsing a large multipart upload — the request is left in an invalid state that request shutdown then treats as valid. The result is an unauthenticated use-after-free.

    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/).