Vulnerability intelligence

Updated 7 minutes ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

80100

Current score

Not much to see here

  1. 1

    CVE-2025-8045 Published Dec 1, 2025

    Hype score

    8

    medium 4.0

    CVE-2025-8045 is a "Use After Free" vulnerability affecting the Arm Ltd Valhall GPU Kernel Driver and Arm 5th Gen GPU Architecture Kernel Driver. This flaw allows a local non-privileged user process to execute improper GPU processing operations, thereby gaining access to memory that has already been freed. The vulnerability impacts driver versions r53p0 through r54p1 for both the Valhall GPU Kernel Driver and the Arm 5th Gen GPU Architecture Kernel Driver. Successful exploitation of this issue can result in the disclosure of kernel memory contents to an unprivileged process running on the device, requiring local access and no user interaction.

  2. 2

    CVE-2026-18577 Published Aug 2, 2026

    Hype score

    7

    high 8.2

    Exploit known

    CVE-2026-18577 is an authentication bypass and account takeover vulnerability affecting N-able N-central versions through 2026.3.1. This flaw is a result of an incomplete patch for a previously identified vulnerability, CVE-2026-18556. Successful exploitation of CVE-2026-18577 allows remote attackers to gain administrative access to vulnerable N-central servers. Once administrative control is established, attackers can abuse the built-in "Take Control" feature to pivot into managed endpoints, deploy scripts, run tools, initiate remote-control sessions, and establish persistence within the compromised environment. The vulnerability impacts both hosted and on-premises deployments of N-able N-central.

  3. 3

    CVE-2025-15039 Published Aug 6, 2026

    Hype score

    4

    critical 9.4

    CVE-2025-15039 describes a vulnerability found in the Conditional Authentication (Adaptive Authentication) script used across several WSO2 products, including API Control Plane, API Manager, Carbon Identity Application Authentication Framework, Identity Server, Identity Server as Key Manager, Open Banking AM, Open Banking IAM, Traffic Manager, and Universal Gateway. This flaw allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation of CVE-2025-15039 can lead to unauthorized access to a targeted user account. This vulnerability is exploitable under specific conditions: the application's login flow must include a particular secondary authenticator, the Conditional Authentication script needs to be configured with specific event callbacks and re-execute an authentication step, the targeted user must have one of the impacted authenticators enrolled, and the attacker must successfully complete any preceding authentication steps.

See more

Insights

See more

Our Security Team's most recent CVE analysis

  1. Link to CVE page

    Intruder Insights

    Updated Aug 7, 2026

    This is a serious vulnerability affecting all supported WordPress versions. It can be exploited by any unauthenticated attacker, and a working proof of concept is available. However, to achieve remote code execution an attacker must trick a WordPress admin into opening a malicious link as part of a social engineering attack. Intruder expects a full exploit to become widely available. This vulnerability is patched in WordPress 7.0.3 (released Aug 6, 2026).

    WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE vulnerability with conditions outside of the attackers control. This requires successful social engineering of and explicit interaction by the target victim. This issue affects all versions of WordPress. Version 7.0.3 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7. Discovered and responsibly disclosed by [the team at pwn.ai](https://pwn.ai/).

  2. CVE-2026-50522

    critical 9.8

    Exploit known

    Link to CVE page

    Intruder Insights

    Updated Jul 21, 2026

    This vulnerability allows an unauthenticated attacker who can access a Sharepoint instance to gain code execution. A patch has been available since July 14th in Microsofts 'Patch Tuesday' security rollup.

    A proof of concept exploit has recently been published and this makes patching more urgent as attacks have now been seen in the wild.

    Deserialization of untrusted data in Microsoft Office SharePoint allows an unauthorized attacker to execute code over a network.

  3. CVE-2026-63030

    critical 9.8

    Exploit known

    Link to CVE page

    Intruder Insights

    Updated Jul 21, 2026

    This is one of two vulnerabilities in a combined chain that allows remote code execution on any stock WordPress installation. CVE-2026-63030 is the entry point — a route confusion bug in the REST API batch endpoint that bypasses authentication, allowing an attacker to invoke internal handlers without any permission check. When combined with CVE-2026-60137, the attacker gains the ability to read any data from the WordPress database with a single HTTP request. An exploit chain has been demonstrated which combines both of these bugs to achieve code execution.

    WordPress 6.9.0–6.9.4 and 7.0.0–7.0.1 are affected. Update to WordPress 6.9.5 or 7.0.2 immediately. No plugins, user interaction, or non-default configuration is required to exploit. Given WordPress powers approximately 43% of all websites, the attack surface is enormous.

    WordPress Core contains a pre-authentication route confusion vulnerability in the REST API batch endpoint that, combined with CVE-2026-60137, allows remote code execution.

    WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.