Vulnerability intelligence

Updated 17 minutes ago

Feeds

Trending now

CVEs trending on social media within the last 24 hours

Hypemeter

100100

Current score

These are not the 0days you are looking for

  1. 1

    CVE-2026-82329 Published Aug 28, 2026

    Hype score

    10

    critical 9.8

    Exploit known

    JFrog Artifactory

    CVE-2026-82329 describes an authentication weakness found in JFrog Artifactory. Under its default configuration, this vulnerability allows an unauthenticated attacker with network access to gain administrative privileges. This flaw is present in various versions of JFrog Artifactory, including those before 7.111.21, and specific ranges within 7.117.0 through 7.117.27, 7.125.0 through 7.125.19, 7.133.0 through 7.133.28, 7.146.0 through 7.146.36/37, and 7.161.0 through 7.161.19.

  2. 2

    CVE-2026-85706 Published Sep 12, 2026

    Hype score

    9

    critical 10.0

    CVE-2026-85706 is a path traversal vulnerability affecting GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw resides within the repository commits API and stems from a combination of improper path confinement and a lack of authentication enforcement. Under specific conditions, an unauthenticated attacker can exploit this vulnerability to read arbitrary files from the affected GitLab server. Successful exploitation of CVE-2026-85706 can lead to the exposure of various sensitive data accessible to the GitLab server process, including configuration details, credentials, secrets, tokens, SSH keys, and database credentials. The vulnerability requires no authentication or user interaction and can be exploited remotely. GitLab released patches for this issue on September 10, 2026, in versions 19.1.8, 19.2.6, and 19.3.2, addressing all affected versions from 18.7 onwards.

  3. 3

    CVE-2026-63375

    Hype score

    5

    Based on available popular articles, a concise description for CVE-2026-63375 cannot be provided as this specific CVE identifier does not appear in the search results. It is possible there may be a typographical error in the requested CVE. However, several similarly numbered CVEs from 2026 were found in the search results, including CVE-2026-3375, CVE-2026-53375, CVE-2026-73375, and CVE-2026-69375.

See more

Known exploited

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

  1. CVE-2026-85706 Published Sep 12, 2026

    Hype score

    9

    critical 10.0

    CVE-2026-85706 is a path traversal vulnerability affecting GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw resides within the repository commits API and stems from a combination of improper path confinement and a lack of authentication enforcement. Under specific conditions, an unauthenticated attacker can exploit this vulnerability to read arbitrary files from the affected GitLab server. Successful exploitation of CVE-2026-85706 can lead to the exposure of various sensitive data accessible to the GitLab server process, including configuration details, credentials, secrets, tokens, SSH keys, and database credentials. The vulnerability requires no authentication or user interaction and can be exploited remotely. GitLab released patches for this issue on September 10, 2026, in versions 19.1.8, 19.2.6, and 19.3.2, addressing all affected versions from 18.7 onwards.

  2. CVE-2026-84869 Published Sep 8, 2026

    Hype score

    1

    critical 9.9

    Exploit known

    CVE-2026-84869 describes a vulnerability found within the ScreenConnect client. This flaw permits the unauthorized transfer and execution of files during an active remote session, bypassing typical authorization or host confirmation processes. It is important to note that this condition specifically affects the ScreenConnect client and does not impact ScreenConnect servers. The vulnerability is associated with improper privilege management and missing authorization.

  3. CVE-2026-42018 Published Aug 12, 2026

    Hype score

    2

    high 7.5

    Exploit known

    CVE-2026-42018 is an improper authentication vulnerability affecting JFrog Artifactory. This flaw allows an unauthenticated caller to obtain an internal anonymous-user token, even when anonymous access is explicitly disabled within the system. The presence of this token could potentially lead to the exposure of sensitive resources within the Artifactory instance. This vulnerability has been observed in active exploitation, often chained with CVE-2026-42016. When combined, these vulnerabilities can enable attackers to escalate privileges and gain administrative control over self-hosted Artifactory servers.

See more

Insights

See more

Our Security Team's most recent CVE analysis

  1. Link to CVE page

    Intruder Insights

    Updated Sep 10, 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. 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.