Vulnerability intelligence

Updated a few seconds ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

800100

Current score

Big chat

  1. 1

    CVE-2026-118306 Published Oct 27, 2026

    Hype score

    80

    critical 9.6

    Google ChromeChromium

    CVE-2026-118306 is a memory corruption vulnerability residing in the FileSystem component of Google Chrome. The flaw affects Google Chrome versions prior to 156.0.8078.73. It is triggered when a user interacts with a specially crafted HTML page, allowing a remote attacker to exploit the underlying memory corruption. If successfully exploited, the vulnerability allows a remote attacker to potentially execute arbitrary code outside of the browser's sandbox environment. The exploit can be initiated over a network without requiring any special privileges, though it does depend on user interaction to be executed. Google has addressed this issue in the 156.0.8078.73 update.

  2. 2

    CVE-2026-118331 Published Oct 27, 2026

    Hype score

    80

    high 8.8

    Google ChromeChromium

    CVE-2026-118331 is a vulnerability affecting Google Chrome and other Chromium-based browsers, such as Microsoft Edge, prior to version 156.0.8078.73. The issue stems from improper input validation within the browser's FileAPI component. A remote attacker could exploit this flaw by convincing a user to visit a specially crafted HTML page, potentially allowing the attacker to execute arbitrary code within the browser's sandboxed environment. The vulnerability was discovered and reported by Anthropic researcher Xinyang Ge, who utilized the Claude AI model to assist in identifying the flaw. Google addressed the issue in late October 2026 with the release of Chrome version 156.0.8078.73/.74 for Windows and macOS, and 156.0.8078.73 for Linux. Users and administrators are advised to update their browsers to the latest version to mitigate the risk of exploitation.

  3. 3

    CVE-2026-118344 Published Oct 27, 2026

    Hype score

    80

    high 8.8

    Google ChromeChromium

    CVE-2026-118344 is a use-after-free vulnerability identified in the Layout component of Google Chrome. Discovered and reported by security researcher Xinyang Ge, the flaw allows a remote attacker to execute arbitrary code within the browser's sandbox environment. This exploitation can be triggered when a user is induced to visit a specially crafted HTML page designed to target the vulnerability. The vulnerability affects Google Chrome versions prior to 156.0.8078.73. Google addressed the issue in a Stable channel update, releasing version 156.0.8078.73/.74 for Windows and macOS, and 156.0.8078.73 for Linux. Users are advised to update their browsers to the latest version to mitigate the risk of potential exploitation.

See more

Known exploited

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

  1. CVE-2026-111357 Published Oct 15, 2026

    high 7.0

    Exploit known

    Ivanti Connect Secure

    CVE-2026-111357 is a privilege escalation vulnerability affecting Ivanti Connect Secure VPN appliances. The flaw stems from the system mishandling how the privileged `dsinvoked` broker trusts configuration data stored in the `DSCache`. By manipulating this trust—specifically by temporarily modifying library code in memory and altering a maintenance task in the configuration store—an attacker with local authenticated access can execute arbitrary code with root-level privileges. Discovered by cybersecurity firm Volexity, this vulnerability was actively exploited in the wild in October 2026 by a threat actor tracked as UTA0576. The attacker chained CVE-2026-111357 with an authentication bypass (CVE-2026-104935) and a predictable-filename weakness (CVE-2026-118527) to achieve unauthenticated root access on fully patched appliances, which they used to harvest Active Directory credentials and sensitive metadata. In response, Ivanti released security patches on October 29, 2026, and the Cybersecurity and Infrastructure Security Agency (CISA) added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog.

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

    Hype score

    16

    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.

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

    high 8.6

    Exploit known

    Cisco Secure Firewall Adaptive Security ApplianceCisco Secure Firewall Threat Defense

    CVE-2026-76418 is a vulnerability affecting the Remote Access SSL VPN service of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software. The issue stems from logic errors—specifically an unchecked return value leading to a NULL pointer dereference—when secondary authentication is configured on a tunnel group. An unauthenticated, remote attacker can exploit this flaw by sending a crafted request while connecting to the SSL remote access VPN, which triggers an unexpected device reload and results in a denial of service (DoS) condition. A successful VPN login is not required to reach the vulnerable code path. In October 2026, Cisco's Product Security Incident Response Team (PSIRT) identified active exploitation of this vulnerability in the wild, prompting the Cybersecurity and Infrastructure Security Agency (CISA) to add it to its Known Exploited Vulnerabilities catalog. While Cisco has released software updates to resolve the issue, there are no official workarounds. Organizations unable to immediately apply the patches can temporarily mitigate the risk by disabling secondary authentication on the default or user-configured tunnel groups.

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