48 vulnerabilities across 15 products scored HIGH or above on June 24, 2026.

  • 🔴 CRITICAL: 20
  • 🟠 HIGH: 28

🔴 [CRITICAL] tryghost/ghost

1 CVE | CVSS 3.1: 9.6 | AAS 15.5

  • cpe:2.3:a:tryghost:ghost:*:*:*:*:*:*:*:*

Ghost CMS by TryGhost is affected by a critical cache poisoning vulnerability (CVE-2026-53943, CVSS 9.6) in versions prior to 6.37.0. An unauthenticated attacker can manipulate the x-ghost-preview header to inject altered content into shared caching layers, causing poisoned responses to be served to all subsequent visitors of the same page. A proof-of-concept exploit is publicly available.

Organizations running Ghost behind a shared cache — including CDNs or reverse proxies — should upgrade to version 6.37.0 or later immediately. Teams unable to patch should review their caching configuration to ensure request-specific headers like x-ghost-preview are not used as part of cached responses. See the vendor advisory at github.com/TryGhost/Ghost for full details.

Vendor Advisory

🔴 [CRITICAL] gogs/gogs

12 CVEs | CVSS 3.1: 10.0 | AAS 15.3

  • cpe:2.3:a:gogs:gogs:*:*:*:*:*:*:*:*

Gogs self-hosted Git service versions prior to 0.14.3 is affected by 12 vulnerabilities, including multiple critical-severity issues up to CVSS 10.0. Among them are path traversal flaws that allow unauthenticated attackers to write repositories to arbitrary filesystem locations and chain Git hook overwrites to achieve remote code execution. Proof-of-concept exploit code is publicly available for at least one of these issues.

Organizations running Gogs should upgrade to version 0.14.3 or later immediately. Given the volume and severity of these flaws, teams unable to patch should restrict network access to Gogs instances and disable public-facing registration. Refer to the vendor commit history and associated advisories on the Gogs GitHub repository for full remediation guidance.

Vendor Advisory

🔴 [CRITICAL] rclone/rclone

1 CVE | CVSS 3.1: 9.8 | AAS 12.9

  • cpe:2.3:a:rclone:rclone:*:*:*:*:*:*:*:*

Rclone versions 1.46.0 through 1.74.2 are affected by a critical unauthenticated remote code execution vulnerability (CVE-2026-49980, CVSS 9.8) in the remote control daemon. When running with the rcd –rc-serve flag, an attacker can craft a single unauthenticated GET or HEAD request using inline remote configuration to execute arbitrary commands on the host during backend initialization. A functional exploit is publicly available, making this an immediate threat.

Any organization using Rclone’s remote control daemon in networked or internet-facing configurations should upgrade to version 1.74.3 or later without delay. If patching is not immediately possible, disable the rcd –rc-serve endpoint or restrict access to trusted networks only. See the vendor advisory at the Rclone GitHub repository for full details.

Vendor Advisory

🔴 [CRITICAL] rocketchat/rocket.chat

6 CVEs | CVSS 3.1: 9.3 | AAS 12.9

  • cpe:2.3:a:rocketchat:rocket.chat:*:*:*:*:*:*:*:*

Rocket.Chat is affected by 6 vulnerabilities, including multiple critical-severity issues up to CVSS 9.3. The most severe is a NoSQL injection flaw in the CAS login handler that allows an unauthenticated attacker to bypass authentication by injecting MongoDB query operators into credential token lookups, with a functional exploit publicly available. Additional vulnerabilities across this batch further expand the attack surface of exposed instances.

Organizations running Rocket.Chat should upgrade immediately to one of the patched versions: 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, or 7.10.11, depending on their release branch. If CAS authentication is not required, disabling it provides an interim mitigation for the most critical issue. See the vendor advisories on the Rocket.Chat GitHub repository for the full list of affected versions and fixes.

Vendor Advisory

🔴 [CRITICAL] appsmithorg/appsmith

2 CVEs | CVSS 3.1: 9.9 | AAS 12.7

  • cpe:2.3:a:appsmithorg:appsmith:*:*:*:*:*:*:*:*

Appsmith versions prior to 2.1 are affected by 2 critical vulnerabilities up to CVSS 9.9, including multiple issues that chain together to escalate impact. The most severe involves the bundled Caddy reverse proxy’s unauthenticated admin API being bound to all interfaces inside the container, which an authenticated low-privileged user can reach via a server-side request forgery flaw to reconfigure the proxy and achieve full system compromise. Proof-of-concept exploit code is publicly available.

Organizations self-hosting Appsmith should upgrade to version 2.1 or later immediately. If patching is not feasible, restrict network access to the Appsmith container and ensure the Caddy admin API on port 2019 is not reachable from untrusted sources. See the vendor advisory on the Appsmith GitHub repository for complete details on both issues.

Vendor Advisory

🔴 [CRITICAL] warpdotdev/warp

8 CVEs | CVSS 3.1: 8.8 | AAS 12.6

  • cpe:2.3:a:warpdotdev:warp:*:*:*:*:*:*:*:*

Warp terminal versions from 0.2023.10.24 through 0.2026.05.06 are affected by 8 vulnerabilities up to CVSS 8.8, including multiple issues related to unsafe handling of local file links and Markdown content. The most severe allows a malicious Markdown document or project to disguise a local-file link as normal rendered content, which when clicked routes executable files to the operating system’s default handler instead of a safe viewer, enabling arbitrary code execution. Functional exploits are publicly available.

Developers and engineering teams using Warp should update to version 0.2026.05.06.15.42.stable_01 or later immediately. Until patched, exercise caution when opening untrusted Markdown files or cloned projects within Warp, and avoid clicking embedded links from unknown sources. Refer to the vendor commits on the Warp GitHub repository for the full scope of fixes across all 8 issues.

Vendor Advisory

🔴 [CRITICAL] mastodon/mastodon

2 CVEs | CVSS 3.1: 8.7 | AAS 12.4

  • cpe:2.3:a:mastodon:mastodon:*:*:*:*:*:*:*:*

Mastodon is affected by 2 vulnerabilities up to CVSS 8.7, including multiple issues that can compromise server-side request integrity. The most severe is a server-side request forgery bypass where an attacker controlling DNS for any domain can publish IPv4-mapped IPv6 address records to circumvent private address checks on instances running Ruby versions older than 3.4, potentially reaching internal services such as loopback, RFC1918 private networks, and link-local addresses. Functional exploits are publicly available.

Administrators running Mastodon instances should upgrade to version 4.5.10, 4.4.17, or 4.3.23 depending on their release branch. As an additional hardening measure, upgrading the underlying Ruby runtime to version 3.4 or later resolves the address validation weakness at its root. See the vendor advisory on the Mastodon GitHub repository for complete details on both vulnerabilities.

Vendor Advisory

🔴 [CRITICAL] jellyfin/jellyfin

2 CVEs | CVSS 3.1: 8.8 | AAS 12.1

  • cpe:2.3:a:jellyfin:jellyfin:*:*:*:*:*:*:*:*

Jellyfin media server versions 10.9.0 through 10.11.9 are affected by 2 vulnerabilities up to CVSS 8.8, including multiple issues exploitable by authenticated non-admin users. The most severe is a path traversal flaw in the client logging endpoint where unsanitized Authorization header fields are used to construct on-disk filenames, allowing any authenticated user to write attacker-controlled content to arbitrary paths on the server and achieve remote code execution. Functional exploits are publicly available.

Self-hosted Jellyfin administrators should upgrade to version 10.11.10 or later immediately. If patching is not immediately possible, restrict user registration and audit existing accounts, as any authenticated user can exploit these flaws regardless of privilege level. See the vendor advisory on the Jellyfin GitHub repository for full technical details on both issues.

Vendor Advisory

🔴 [CRITICAL] proftpd_project/proftpd

1 CVE | CVSS 4.0: 8.6 | AAS 12.1

  • cpe:2.3:a:proftpd:proftpd:*:*:*:*:*:*:*:*

ProFTPD versions through 1.3.9b and 1.3.10rc2 are affected by a critical access control bypass vulnerability (CVE-2026-35025, CVSS 8.6). An authenticated FTP user can circumvent Directory ACL restrictions, including DenyAll-protected directories, by prefixing paths with /proc/self/root in rename commands, exploiting unresolved symlink handling to bypass lexical path comparisons and access or manipulate restricted files. A functional exploit is publicly available.

Organizations running ProFTPD should monitor proftpd.org for a patched release and apply it as soon as available. In the interim, restrict FTP user access to trusted accounts, consider disabling the RNFR command where feasible, and audit any sensitive directories relying solely on ProFTPD Directory ACLs for protection. Environments running ProFTPD on Linux are particularly exposed due to the /proc/self/root symlink behavior.

Vendor Advisory

🔴 [CRITICAL] cacti/cacti

4 CVEs | CVSS 3.1: 9.8 | AAS 12.1

  • cpe:2.3:a:cacti:cacti:*:*:*:*:*:*:*:* (< 1.2.31)

Cacti network monitoring framework version 1.2.30 and prior is affected by 4 vulnerabilities up to CVSS 9.8, including multiple critical-severity issues. The most severe is an unauthenticated local file inclusion flaw exploitable through the graph theme and rrdtool IPC serialization mechanisms, requiring no credentials to access sensitive files on the server. Proof-of-concept exploit code is publicly available.

Organizations running Cacti should upgrade to version 1.2.31 or later immediately, as the unauthenticated nature of the lead vulnerability makes internet-facing instances especially at risk. If patching cannot be performed promptly, restrict network access to Cacti instances to trusted management networks only. See the vendor commits on the Cacti GitHub repository for complete details on all four issues.

Vendor Advisory

🟠 [HIGH] feast-dev/feast

1 CVE | CVSS 4.0: 9.3 | AAS 11.7

  • cpe:2.3:a:feast-dev:feast:*:*:*:*:*:*:*:*

Feast feature store versions prior to 0.63.0 are affected by a high-severity unsafe deserialization vulnerability (CVE-2026-56121, CVSS 9.3). An unauthenticated attacker can achieve remote code execution by sending a crafted gRPC request to the registry server, where a base64-encoded payload is passed directly to Python’s dill.loads() before any authorization check, allowing arbitrary OS command execution. A functional exploit is publicly available.

ML engineering and platform teams running Feast with an exposed registry server should upgrade to version 0.63.0 or later immediately. If patching is not feasible, restrict network access to the Feast gRPC registry endpoint to trusted clients only, as no authentication is required to exploit this flaw. See the vendor commit on the Feast GitHub repository for full remediation details.

Vendor Advisory

🟠 [HIGH] lepture/mistune

1 CVE | CVSS 4.0: 8.7 | AAS 11.1

  • cpe:2.3:a:lepture:mistune:*:*:*:*:*:*:*:* (< 3.3.0)

Mistune Python Markdown parser versions prior to 3.3.0 are affected by a high-severity CPU exhaustion denial-of-service vulnerability (CVE-2026-49851, CVSS 8.7). Attacker-controlled Markdown input containing many consecutive open-bracket characters triggers quadratic-time behavior in the link text parser, allowing a single crafted payload to consume excessive CPU resources and render the application unresponsive. A functional exploit is publicly available.

Development and platform teams using Mistune to process user-supplied or untrusted Markdown content should upgrade to version 3.3.0 or later immediately. Applications particularly at risk include web platforms, comment systems, and documentation tools where external users can submit Markdown for rendering. See the vendor advisory on the Mistune GitHub repository for full details.

Vendor Advisory

🟠 [HIGH] style-dictionary/style-dictionary

1 CVE | CVSS 3.1: 8.8 | AAS 11.1

  • cpe:2.3:a:style-dictionary:style-dictionary:*:*:*:*:*:*:*:*

Style Dictionary versions 4.3.0 through 5.4.3 are affected by a high-severity prototype pollution vulnerability (CVE-2026-54639, CVSS 8.8). The flaw is triggered through multiple paths including direct use of the convertTokenData function, the Expand API, and the standard transform lifecycle, with the highest impact occurring when Style Dictionary is integrated into a Node.js server application where prototype pollution can lead to denial of service or remote code execution. A functional exploit is publicly available.

Front-end platform and design systems teams using Style Dictionary should upgrade to version 5.4.4 or later immediately. Server-side integrations are at greatest risk and should be prioritized for patching, while CLI and build-time-only usage carries moderate but still actionable risk. See the vendor commit on the Style Dictionary GitHub repository for full remediation details.

Vendor Advisory

🟠 [HIGH] siyuan-note/siyuan

5 CVEs | CVSS 3.1: 9.9 | AAS 10.7

  • cpe:2.3:a:siyuan-note:siyuan:*:*:*:*:*:*:*:*

SiYuan personal knowledge management system versions prior to 3.7.0 are affected by 5 vulnerabilities up to CVSS 9.9, including multiple cross-site scripting and injection flaws. The most severe allows an attacker to inject malicious JavaScript through unsanitized database cell content, which executes when a victim opens the block-attribute panel, and on Electron desktop builds this escalates to full system compromise due to nodeIntegration being enabled in the renderer. Proof-of-concept exploit code is publicly available.

Users running SiYuan, particularly the Electron desktop application, should upgrade to version 3.7.0 or later immediately. Until patched, avoid opening shared notebooks or importing content from untrusted sources, as exploitation requires only that a victim view a crafted database cell. See the vendor advisories on the SiYuan GitHub repository for complete details on all five issues.

Vendor Advisory

🟠 [HIGH] getsentry/sentry

1 CVE | CVSS 3.1: 7.5 | AAS 9.3

  • cpe:2.3:a:getsentry:sentry:*:*:*:*:*:*:*:*

Sentry error tracking and performance monitoring platform versions 24.4.0 through 26.5.1 are affected by a high-severity Regular Expression Denial of Service vulnerability (CVE-2026-52794, CVSS 7.5). A remote attacker can craft event payloads with malicious field values that trigger catastrophic regex backtracking in the event ingestion pipeline, consuming excessive CPU resources and potentially degrading or disrupting monitoring capabilities. This vulnerability is confirmed exploitable.

Organizations self-hosting Sentry should upgrade to version 26.5.2 or later immediately, as the ingestion pipeline is directly exposed to attacker-controlled input. Disruption of error tracking infrastructure can blind teams to production incidents, making this a high-priority patch even in environments not directly internet-facing. See the vendor pull request on the Sentry GitHub repository for full fix details.

Vendor Advisory