Vulnerability intelligence

Updated an hour ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

230100

Current score

Not much chatter

  1. 1

    CVE-2025-65200 Published Oct 22, 2026

    Hype score

    23

    critical 9.6

    DockerLocalStack

    CVE-2025-65200 is a vulnerability identified in LocalStack, a platform that emulates Amazon Web Services (AWS) cloud environments for local development. The issue specifically affects version 4.9.2 of the software and allows for arbitrary code execution within the context of the running LocalStack Docker container. The vulnerability can be exploited by hosting crafted content on a web-accessible URL and passing that URL as the `templateURL` parameter to the `_localstack/cloudformation/deploy` endpoint. When the endpoint processes this input, the hosted content is executed inside the container, enabling attackers to run unauthorized commands.

  2. 2

    CVE-2026-46300 Published May 23, 2026

    Hype score

    22

    high 7.8

    Exploit known

    AWSUbuntuCloudContainer SecurityTunneling protocolFragnesia

    CVE-2026-46300, dubbed "Fragnesia," is a local privilege escalation (LPE) vulnerability found in the Linux kernel's XFRM ESP-in-TCP subsystem. This flaw allows an unprivileged local attacker to perform arbitrary byte writes into the kernel page cache of read-only files. The vulnerability arises from a logic error where `skb_try_coalesce()` fails to propagate the `SKBFL_SHARED_FRAG` marker, causing the kernel to lose track of externally backed fragments. This page-cache corruption can be exploited to modify the in-memory cached copies of read-only files, such as `/usr/bin/su`, enabling an unprivileged process to gain root privileges. Fragnesia is the third LPE vulnerability discovered by William Bowling of the V12 security team in the same general area of the Linux kernel (IPsec ESP / rxrpc), following "Copy Fail" and "Dirty Frag." A public proof-of-concept exploit for CVE-2026-46300 is available.

  3. 3

    CVE-2026-41709 Published Jul 30, 2026

    Hype score

    22

    low 2.7

    Exploit known

    Server

    CVE-2026-41709 is an insufficient logging vulnerability affecting Broadcom's VMware ESX bare-metal hypervisor. Disclosed and patched by Broadcom in July 2026, the flaw allows a malicious actor with administrative privileges to perform certain operations without them being recorded in the system logs. In October 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog following reports of active exploitation in the wild. According to cybersecurity researchers at CrowdStrike, a China-nexus cyber espionage group known as Warp Panda exploited this vulnerability as a zero-day in early 2026. The threat actor targeted U.S. organizations, particularly within the legal sector, using the flaw to reduce audit trail visibility and cover their tracks. By bypassing audit logging, the group was able to hinder forensic reconstruction and maintain persistent, covert access to compromised environments.

See more

Known exploited

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

  1. CVE-2026-97229 Published Oct 13, 2026

    critical 10.0

    Exploit known

    GitLabGitLab CEGitLab EE

    CVE-2026-97229 is an integer overflow vulnerability (CWE-190) located in the CI/CD Regular Expression Compiler of GitLab Community Edition (CE) and Enterprise Edition (EE). The flaw stems from insufficient validation of regular expressions used within project pipeline configurations. Under certain conditions, an unauthenticated remote attacker can exploit this vulnerability by supplying a specially crafted regular expression in a CI/CD configuration file (such as `.gitlab-ci.yml`), which can lead to arbitrary code execution on the affected GitLab server. The vulnerability affects self-managed GitLab versions 19.1 through 19.2.7, 19.3 through 19.3.3, and 19.4 through 19.4.1. Security researchers note that exploitation typically requires the ability to commit a configuration file to a repository. However, this constraint is bypassed on instances where self-registration and project creation are enabled for new users. GitLab has addressed the issue in versions 19.4.2, 19.3.4, and 19.2.8, and there have been no confirmed reports of active exploitation in the wild.

  2. CVE-2026-76418 Published Oct 28, 2026

    high 8.6

    Exploit known

    A vulnerability in the Remote Access SSL VPN service of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial of service (DoS) condition. This vulnerability is due to logic errors when secondary authentication is configured on a tunnel group. An attacker could exploit this vulnerability by sending a crafted request when connecting to the SSL remote access VPN. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition.

  3. CVE-2026-46300 Published May 23, 2026

    Hype score

    22

    high 7.8

    Exploit known

    AWSUbuntuCloudContainer SecurityTunneling protocolFragnesia

    CVE-2026-46300, dubbed "Fragnesia," is a local privilege escalation (LPE) vulnerability found in the Linux kernel's XFRM ESP-in-TCP subsystem. This flaw allows an unprivileged local attacker to perform arbitrary byte writes into the kernel page cache of read-only files. The vulnerability arises from a logic error where `skb_try_coalesce()` fails to propagate the `SKBFL_SHARED_FRAG` marker, causing the kernel to lose track of externally backed fragments. This page-cache corruption can be exploited to modify the in-memory cached copies of read-only files, such as `/usr/bin/su`, enabling an unprivileged process to gain root privileges. Fragnesia is the third LPE vulnerability discovered by William Bowling of the V12 security team in the same general area of the Linux kernel (IPsec ESP / rxrpc), following "Copy Fail" and "Dirty Frag." A public proof-of-concept exploit for CVE-2026-46300 is available.

See more

Insights

See more

Our Security Team's most recent CVE analysis

  1. CVE-2026-118633

    critical 9.2

    Link to CVE page

    Intruder Insights

    Updated Oct 29, 2026

    This vulnerability allows a remote attacker who can determine that an email server is using Sophos UTM's email scanning feature to obtain code execution on the UTM appliance as admin/root.

    The patch must be applied manually and this should be done as soon as possible. As a mitigation if you are unable to patch immediately, you should disable the email scanning feature.

    A path traversal vulnerability allows a remote unauthenticated attacker to execute arbitrary code as root in Sophos UTM (all versions) after winning a race condition by sustaining repeated attacks for a few minutes when the email proxy is used with scanning enabled. Sophos UTM is end-of-life and the patch must be installed manually.

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

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