Vulnerability intelligence

Updated 22 minutes ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

190100

Current score

Pretty quiet out there

  1. 1

    CVE-2026-43499 Published May 21, 2026

    Hype score

    19

    high 7.8

    Linux KernelRtmutex

    CVE-2026-43499, publicly known as GhostLock, is a local privilege escalation vulnerability found within the Linux kernel. This flaw resides specifically in the `rtmutex` (real-time mutex) and Priority Inheritance (PI) futex requeue path. The core issue stems from an incorrect cleanup operation during a 'proxy-lock rollback' in the futex requeue process, where the system operates on the currently executing task instead of the true waiter task. This misdirection leaves behind stale priority-inheritance state and creates a use-after-free (UAF) condition, where the kernel attempts to use memory that has already been released. An attacker with local code execution can exploit this vulnerability to gain elevated privileges or execute unauthorized code on affected systems. The vulnerability was introduced in Linux 2.6.39 in May 2011 and affects kernels up to version 7.1.

  2. 2

    CVE-2026-97229 Published Oct 13, 2026

    Hype score

    17

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

    CVE-2025-3248 Published Apr 7, 2025

    Hype score

    17

    critical 9.8

    Exploit known

    LangflowAPI

    CVE-2025-3248 is a code injection vulnerability that affects Langflow versions prior to 1.3.0. It exists in the `/api/v1/validate/code` endpoint, where a remote, unauthenticated attacker can send crafted HTTP requests to execute arbitrary code on the server. This vulnerability allows attackers to gain control of vulnerable Langflow servers without needing authentication. To remediate this vulnerability, users are advised to upgrade to Langflow version 1.3.0 or restrict network access to the application.

See more

Insights

See more

Our Security Team's most recent CVE analysis

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

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

  3. Link to CVE page

    Intruder Insights

    Updated Nov 3, 2026

    A malicious web page can exploit this use-after-free in Chrome's Layout engine to run code, but only inside the browser sandbox, so on its own it doesn't give an attacker access to the user's machine. The risk is higher for automated browsers that run without the  sandbox, such as Playwright by default, where the same exploit runs directly on the host. 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 Layout in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)