Vulnerability intelligence

Updated an hour ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

480100

Current score

Soft-boiled

  1. 1

    CVE-2026-123007 Published Nov 18, 2026

    Hype score

    48

    critical 9.2

    NGINX PlusNGINX Open Source

    CVE-2026-123007 is an integer underflow vulnerability in NGINX's HTTP/2 flow-control implementation, disclosed in November 2026 as part of a group of flaws dubbed "NGINX2Root". The issue arises when a remote, unauthenticated client cancels queued response data. NGINX fails to verify the HTTP/2 maximum limit when refunding queued bytes to the connection's send window, resulting in an integer underflow. This miscalculation allows invalid window values to propagate, causing NGINX to use an incorrect length during subsequent memory-copy operations and leading to a heap-based out-of-bounds write. Exploiting this memory corruption can crash NGINX worker processes, leading to a denial of service, or potentially allow remote code execution (RCE) with the privileges of the worker process. However, achieving RCE is complex and requires transmitting a massive volume of HTTP/2 traffic (approximately 128 GB) over a direct connection, as well as bypassing memory protection mechanisms like Address Space Layout Randomization (ASLR). The vulnerability affects NGINX configurations where HTTP/2 is enabled. Organizations can address the issue by upgrading to a patched version of NGINX and restarting the service, or temporarily mitigate it by disabling HTTP/2 on exposed listeners.

  2. 2

    CVE-2026-123633 Published Nov 18, 2026

    Hype score

    36

    critical 9.2

    NGINX PlusNGINX Open Source

    CVE-2026-123633 is a use-after-free vulnerability affecting NGINX Plus and NGINX Open Source when configured to use HTTP/2 with requests forwarded to an upstream backend server. The flaw stems from a connection-lifecycle issue where an active HTTP/2 connection can remain incorrectly marked as reusable. Specifically, a connection that has only received a partial HEADERS frame is marked reusable, and this status is not consistently cleared when a new request stream begins processing. Under connection-resource pressure—such as when the server is running low on worker connections—NGINX may reclaim and release the memory of the active connection while it is still being used to connect to an upstream server, resulting in a use-after-free condition. This vulnerability can allow an unauthenticated remote attacker to cause a denial-of-service (DoS) or potentially execute arbitrary code with the privileges of the NGINX worker process. The bug dates back to NGINX version 1.19.7 (released in 2021) and was patched in November 2026 in NGINX Open Source versions 1.31.9 and 1.30.7, as well as NGINX Plus versions 37.2.0.1 and 37.0.7.1. For systems where immediate patching is not possible, disabling HTTP/2 on exposed listeners serves as a temporary mitigation.

  3. 3

    CVE-2026-123634 Published Nov 18, 2026

    Hype score

    35

    critical 9.2

    NGINX PlusNGINX Open Source

    CVE-2026-123634 is a use-after-free vulnerability affecting NGINX Open Source and NGINX Plus when configured as a proxy. The flaw resides in the DNS resolver's waiting list processing and is triggered under specific configuration conditions. Specifically, it occurs when the proxied server name is built using variables (request-time DNS) and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves that same server name. When a request and its mirror subrequest wait for the same lookup, a specially crafted HTTP request can trigger the use-after-free condition in the NGINX worker process. Exploitation of this vulnerability can allow an unauthenticated remote attacker to crash the NGINX worker process, corrupt its memory, or potentially achieve remote code execution (RCE) if Address Space Layout Randomization (ASLR) is disabled or bypassed. To address the issue, F5 released patches in NGINX Open Source versions 1.31.9 and 1.30.7, as well as NGINX Plus versions 37.3.0.1 and 37.0.8.1. Temporary workarounds include avoiding the use of SSI and mirror directives, or pointing the `proxy_pass` directive to a fixed upstream group to eliminate request-time DNS lookups.

See more

Known exploited

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

  1. CVE-2026-90817 Published Sep 20, 2026

    critical 9.8

    Exploit known

    REDCap

    CVE-2026-90817 describes an unauthenticated Remote Code Execution (RCE) vulnerability affecting REDCap versions 13.3.0 and higher. This flaw resides within the survey passthrough routing and Data Import processing logic of the software. A malicious actor could exploit this vulnerability by manipulating HTTP requests to access an unintended controller route from a public survey context. This is achieved by supplying a specially crafted file-path or stream parameter during the import handling process. Successful exploitation allows for the remote execution of arbitrary code on the REDCap server, though knowledge of a valid public survey hash is required.

  2. CVE-2026-90436 Published Nov 6, 2026

    critical 9.8

    Exploit known

    ** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> element is also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. The fault is parsed while the engine resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. This affects all Apache Axis 1.x versions through 1.4. As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.

  3. CVE-2026-40217 Published Apr 10, 2026

    high 8.8

    Exploit known

    LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.

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)