Vulnerability intelligence

Updated 34 minutes ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

230100

Current score

These are not the 0days you are looking for

  1. 1

    CVE-2026-67276 Published Sep 5, 2026

    Hype score

    23

    critical 9.2

    RouterOSSSH

    CVE-2026-67276 is an SSH authentication bypass vulnerability affecting MikroTik RouterOS. The flaw stems from an incomplete verification process of RSA public keys during SSH authentication. Specifically, RouterOS checks the key type and modulus but fails to compare the entire RSA public key, omitting the exponent. This oversight allows an attacker, who possesses knowledge of a user's public modulus, to forge a different key and successfully log in via SSH without needing the corresponding private key. This vulnerability has been actively exploited as part of a larger attack chain dubbed "MikroTrick" and has been addressed in RouterOS versions 6.49.21 (Long-term), 7.23.4 (Long-term), and 7.24.2 (Stable).

  2. 2

    CVE-2026-85046 Published Sep 3, 2026

    Hype score

    11

    high 8.8

    Exploit known

    ChromiumGoogle ChromeV8

    CVE-2026-85046 is identified as a type confusion vulnerability residing within V8, the JavaScript and WebAssembly engine utilized by Google Chrome. This flaw enables a remote attacker to execute arbitrary code within the browser's sandbox by enticing a user to visit a specially crafted HTML page. The technical root cause of this vulnerability involves a bug in the V8 compilers, which leads to an array containing `PACKED_ELEMENTS` incorrectly receiving the map `PACKED_SMI_ELEMENTS`. This misclassification can be exploited to achieve arbitrary read and write capabilities on the JavaScript heap. The vulnerability was discovered and reported by security researcher Salvatore Gulizia (aka Serotav) on August 4, 2026, and affects Google Chrome versions prior to 152.0.7977.82. Google has released updates to address this issue, and has acknowledged that an exploit for CVE-2026-85046 exists in the wild.

  3. 3

    CVE-2026-19174 Published Aug 6, 2026

    Hype score

    11

    high 8.8

    Google ChromeV8Chromium

    CVE-2026-19174 is an integer overflow vulnerability found within the V8 JavaScript engine of Google Chrome. This flaw, categorized as CWE-190, affects versions of Google Chrome prior to 151.0.7922.109. Successful exploitation of this vulnerability could allow a remote attacker to execute arbitrary code within the browser's context. This typically occurs if a user is enticed to interact with a specially crafted webpage.

See more

Known exploited

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

  1. CVE-2026-85046 Published Sep 3, 2026

    Hype score

    11

    high 8.8

    Exploit known

    V8ChromiumGoogle Chrome

    CVE-2026-85046 is identified as a type confusion vulnerability residing within V8, the JavaScript and WebAssembly engine utilized by Google Chrome. This flaw enables a remote attacker to execute arbitrary code within the browser's sandbox by enticing a user to visit a specially crafted HTML page. The technical root cause of this vulnerability involves a bug in the V8 compilers, which leads to an array containing `PACKED_ELEMENTS` incorrectly receiving the map `PACKED_SMI_ELEMENTS`. This misclassification can be exploited to achieve arbitrary read and write capabilities on the JavaScript heap. The vulnerability was discovered and reported by security researcher Salvatore Gulizia (aka Serotav) on August 4, 2026, and affects Google Chrome versions prior to 152.0.7977.82. Google has released updates to address this issue, and has acknowledged that an exploit for CVE-2026-85046 exists in the wild.

  2. CVE-2026-48710 Published May 26, 2026

    medium 6.5

    Exploit known

    StarlettePort (443)

    Starlette is a lightweight ASGI framework/toolkit. Prior to version 1.0.1, the HTTP `Host` request header was not validated before being used to reconstruct `request.url`. Because the routing algorithm relies on the raw HTTP path while `request.url` is rebuilt from the `Host` header, a malformed header could make `request.url.path` differ from the path that was actually requested. Middleware and endpoints that apply security restrictions based on `request.url` (rather than the raw `scope` path) could therefore be bypassed. Users should upgrade to a version greater than or equal to version 1.0.1, which validates the `Host` header against the grammar of RFC 9112 §3.2 / RFC 3986 §3.2.2 when constructing `request.url` and falls back to `scope["server"]` for malformed values.

  3. CVE-2026-49869 Published Jun 26, 2026

    critical 10.0

    Exploit known

    Kestra OSSplugin-script-shellKestra

    Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, AuthenticationFilter in Kestra OSS uses request.getPath().endsWith("/configs") to whitelist the public configuration endpoint from Basic Auth. Because the check is a suffix match rather than an exact path match, any API path whose last segment is configs bypasses authentication entirely. An unauthenticated remote attacker can exploit this to create and execute arbitrary workflows without credentials. Because Kestra ships with script execution plugins (plugin-script-shell, plugin-script-python, etc.) enabled by default, this directly results in unauthenticated Remote Code Execution as root inside the Kestra worker container. This vulnerability is fixed in 1.0.45 and 1.3.21.

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.