Vulnerability intelligence

Updated an hour ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

300100

Current score

It's warming up

  1. 1

    CVE-2026-129474 Published Nov 19, 2026

    Hype score

    30

    critical 9.2

    PHP

    CVE-2026-129474 is a use-after-free vulnerability affecting PHP version 8.5 and later. The flaw occurs when PHP attempts to collect arguments for a backtrace from a method handled by the magic methods `__call()` or `__callStatic()`, leading to the application accessing freed memory. An unauthenticated attacker can exploit this by sending a crafted request that triggers a fatal error while the application is executing one of these magic methods. If successfully exploited, the vulnerability can allow the attacker to execute arbitrary code with the privileges of the PHP worker process. For an attack to succeed, specific configuration settings must be active: the PHP environment must have `fatal_error_backtraces` enabled (which is the default in PHP 8.5) and `zend.exception_ignore_args` set to 0. Additionally, the attacker must control enough request data to influence memory allocation and reach a magic method call that triggers a fatal error. The vulnerability has been resolved in PHP versions 8.5.13 and 8.6.0. Temporary mitigations include disabling fatal error backtraces or setting `zend.exception_ignore_args` to 1.

  2. 2

    CVE-2026-129182 Published Nov 19, 2026

    Hype score

    28

    critical 9.2

    PHPApachePHP-FPM

    CVE-2026-129182 is a use-after-free vulnerability in PHP that stems from an incomplete fix for a previous flaw, CVE-2026-109619. The issue affects PHP 8.5 releases prior to version 8.5.13, where a global variable tracking fatal error backtraces can be repopulated during the shutdown process after the executor has already been cleaned up. This repopulation can occur when PHP restores modified INI settings—such as conflicting memory limits or compression configurations—which triggers a fatal diagnostic that recreates the backtrace. Once the request heap is released, a subsequent request handled by the same worker can access this stale backtrace before normal executor initialization, leading to memory corruption and potential remote code execution. The vulnerability primarily impacts environments using PHP-FPM or mod_php under specific configurations. To exploit the flaw, an attacker must trigger a diagnostic before executor initialization in a subsequent request handled by the same worker. The PHP Foundation addressed this issue in PHP 8.5.13 and 8.6.0 by ensuring that PHP no longer creates or consumes the fatal-error backtrace while the executor is inactive. As a temporary mitigation, administrators can disable fatal error backtraces by setting `fatal_error_backtraces=0` in their configuration.

  3. 3

    CVE-2026-115560 Published Nov 19, 2026

    Hype score

    26

    critical 9.2

    CVE-2026-115560 is a remote code execution (RCE) vulnerability in PHP's session upload progress feature, which was disclosed by the PHP project in October 2026. The vulnerability stems from the inconsistent handling of session data when an application changes its serialization formats during request processing. It specifically affects environments where the `session.serialize_handler` is initially configured as `php_binary` or `php_serialize`, but is subsequently changed to `php` at runtime using `ini_set()` before `session_start()` is called, while the session upload progress feature remains active. Because this vulnerability requires a highly specific and uncommon combination of configuration settings and application code, the PHP security team has characterized it as an unlikely vector in practice. As a result, the issue is being addressed through PHP's routine release cycle rather than an emergency patch. Until a formal update is released, the recommended mitigation is to disable the session upload progress feature by setting `session.upload_progress.enabled = 0` in the PHP configuration.

See more

Known exploited

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

  1. CVE-2026-76466 Published Oct 21, 2026

    critical 9.8

    Exploit known

    A vulnerability in the database service feature of Cisco Expressway Series could allow an unauthenticated, remote attacker with network access to a Cisco Expressway device to execute arbitrary operating system commands as root. This vulnerability is due to the use of persistent cookies. Additionally, there is insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering, which means that client certificates are not validated. An attacker with possession of the cookies could exploit this vulnerability by connecting to the database service and invoking specific remote procedure call (RPC) commands. A successful exploit could allow the attacker to execute arbitrary commands as root on the underlying operating system of an affected device. Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices.

  2. CVE-2026-129448 Published Nov 17, 2026

    critical 9.8

    Exploit known

    Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. Users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.

  3. CVE-2026-123890 Published Nov 19, 2026

    critical 9.8

    Exploit known

    VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service. Affected versions: 9.1.x (fixed in 9.1.1.0200); 9.0.x (fixed in 9.0.2.0200); 8.0 (fixed in 8.0 U3m); 5.x (fixed in 5.2.5). Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 are also affected (see KB463116).

See more

Insights

See more

Our Security Team's most recent CVE analysis

  1. Link to CVE page

    Intruder Insights

    Updated Nov 18, 2026

    Java4Shell is a weakness in Java OpenJDK which allows an attacker to corrupt memory. The weakness exists in OpenJDK's Base64 decoder, and malformed input allows overwriting memory in an unsafe manner which could allow an unauthenticated attacker to run code or leak memory.

    Not all hardware is affected. In particular, the exploit needs the system to be using a x86-64 processor with AVX-512 VBMI support, and ARM64 CPUs are not affected. Additionally, for the attacker to succeed, the exploit must be specifically tailored to the target. For these reasons, targeted exploitation is more likely than mass exploitation, and many systems will not be exploitable.

    The exploit has been proven in test environments but it will also be susceptible to network jitter and machine configuration on real hosts, making an attacker's job significantly harder.These factors echo what we saw with PHP2Shell, which was in practice difficult to pull off for similar reasons.

    Patching is still important, since if your systems use vulnerable hardware and are targeted directly and with sustained effort, exploitation will be possible

    Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler). Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

  2. Link to CVE page

    Intruder Insights

    Updated Nov 3, 2026

    Exploiting this FileAPI flaw requires a user to visit a malicious web page, and a successful attack runs code inside Chrome's sandbox rather than on the underlying system. An attacker could still gain full code execution on the host by chaining it with a sandbox  escape such as CVE-2026-118306, or by targeting an automated browser running with the sandbox disabled. No exploitation has been reported; update Chrome to 156.0.8078.73 or later, along with other Chromium-based browsers and Electron apps.

    Use after free in FileAPI in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

  3. Link to CVE page

    Intruder Insights

    Updated Nov 3, 2026

    Chrome uses Skia to render graphics, and a crafted web page can abuse this input validation flaw to run code inside the browser sandbox. For most users the sandbox limits the impact, but automated browsers running without it, such as Playwright by default, are  exposed to code execution on the host. No exploitation has been reported; update Chrome to 156.0.8078.73 or later, along with any other browser or app that bundles Chromium.

    Integer overflow in Skia in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)