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

  • 🔴 CRITICAL: 4
  • 🟠 HIGH: 46

Exploit Status Upgrades

The following CVEs from previous bulletins have been upgraded based on new exploit intelligence:

  • [UPGRADED] CVE-2026-48909 (joomshaper.net/sp_lms_extension_for_joomla) — F1: exploitable → functional, AAS: 9.8 → 11.8 (HIGH → HIGH). Originally in 2026-06-20 bulletin.
    • X trend: 1 exploit mentions in 2 tweets
  • [UPGRADED] CVE-2026-54005 (getkirby/cms) — F1: exploitable → functional, AAS: 9.3 → 11.3 (HIGH → HIGH). Originally in 2026-06-18 bulletin.
    • X trend: 3 exploit mentions in 3 tweets

🔴 [CRITICAL] warpdotdev/warp

8 CVEs | CVSS 3.1: 8.8 | AAS 12.6

  • cpe:2.3:a:warpdotdev:warp:*:*:*:*:*:*:*:* (>= 0.2025.10.08.08.12.stable_00, < 0.2026.05.06.15.42.stable_01)
  • cpe:2.3:a:warpdotdev:warp:*:*:*:*:*:*:*:* (>= 0.2021.04.25.23.05.stable_00, < 0.2026.05.06.15.42.stable_01)
  • cpe:2.3:a:warpdotdev:warp:*:*:*:*:*:*:*:* (>= 0.2025.03.05.08.02.stable_00, < 0.2026.05.06.15.42.stable_01)

Warp, the agentic development environment by warpdotdev, is affected by eight vulnerabilities, including multiple critical-severity issues with a CVSS score of 8.8. The lead vulnerability allows attackers to craft malicious Markdown documents containing local-file links that, when clicked by a user, cause Warp to route executable files to the operating system’s default file handler rather than restricting actions to safe viewers. A functional exploit exists for at least one of these issues, significantly increasing the risk of real-world attacks. Versions from 0.2023.10.24.08.03.stable_00 through 0.2026.05.06.15.42.stable_01 are affected.

Security teams managing environments where Warp is used as a terminal or development tool should prioritize this update immediately. Apply the fix referenced in the vendor advisory at the linked GitHub commit, ensure all instances are updated past the vulnerable version range, and caution users against opening untrusted Markdown files or project directories in Warp until patching is confirmed.

Vendor Advisory

🔴 [CRITICAL] mastodon/mastodon

2 CVEs | CVSS 3.1: 8.7 | AAS 12.4

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

Mastodon, the open-source ActivityPub-based social network server, is affected by two vulnerabilities, including at least one critical-severity issue with a CVSS score of 8.7. The lead vulnerability allows an attacker who controls DNS for any domain to bypass server-side request forgery protections by publishing AAAA records with IPv4-mapped IPv6 addresses, causing the PrivateAddressCheck to incorrectly classify private addresses as public. This can expose loopback, RFC1918 private networks, and link-local address space to attacker-initiated requests. A functional exploit exists, and instances running Ruby versions older than 3.4 are particularly at risk.

Administrators operating Mastodon instances should upgrade immediately to version 4.5.10, 4.4.17, or 4.3.23 depending on their release track. Additionally, upgrading the underlying Ruby runtime to 3.4 or later provides defense in depth against this class of SSRF bypass. Refer to the vendor security advisory for full details.

Vendor Advisory

🟠 [HIGH] gogs/gogs

12 CVEs | CVSS 3.1: 10.0 | AAS 11.8

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

Gogs, the open-source self-hosted Git service, is affected by twelve vulnerabilities, including multiple critical-severity issues with a maximum CVSS score of 10.0. The lead vulnerability allows attackers to create organizations with path traversal sequences in their names, enabling arbitrary filesystem writes that can be chained to overwrite Git hook configurations and achieve remote code execution. Multiple additional flaws compound the risk, and exploitation is considered feasible with available technical details.

Organizations running self-hosted Gogs instances should treat this as an urgent priority and upgrade to version 0.14.3 or later immediately. Given the severity and volume of issues, any internet-exposed Gogs instance running a prior version should be considered at high risk of compromise. Review the vendor advisory and referenced commit for full remediation guidance.

Vendor Advisory

🟠 [HIGH] siyuan-note/siyuan

7 CVEs | CVSS 3.1: 9.9 | AAS 11.2

  • cpe:2.3:a:siyuan-note:siyuan:*:*:*:*:*:*:*:* (< 3.7.0)

SiYuan, an open-source personal knowledge management system by siyuan-note, is affected by seven vulnerabilities, including multiple critical-severity issues with a maximum CVSS score of 9.9. The lead vulnerability is a stored cross-site scripting flaw in the attribute-view cell renderer, where unsanitized cell content in text, URL, phone, and asset fields allows arbitrary JavaScript execution when a victim opens the block-attribute panel. On Electron desktop builds, the renderer runs with node integration enabled, escalating this from a browser-context XSS to full system-level code execution.

Teams and individuals using SiYuan, particularly the Electron desktop application, should upgrade to version 3.7.0 or later immediately. Until patched, users should avoid opening shared notebooks or importing content from untrusted sources, as exploitation requires only that a victim view a crafted database cell. Refer to the vendor security advisory for complete details on all seven issues.

Vendor Advisory

🟠 [HIGH] appsmithorg/appsmith

2 CVEs | CVSS 3.1: 9.9 | AAS 11.2

  • cpe:2.3:a:appsmithorg:appsmith:*:*:*:*:*:*:*:* (< 2.1)

Appsmith, an open-source platform for building admin panels, internal tools, and dashboards, is affected by two vulnerabilities, including at least one critical-severity issue with a maximum CVSS score of 9.9. The lead vulnerability exposes the bundled Caddy reverse proxy’s unauthenticated admin API on 0.0.0.0:2019 inside the container, which an authenticated low-privileged user can reach through a server-side request forgery chain to issue arbitrary admin API calls, including loading new configurations. This effectively allows a low-privileged user to reconfigure the reverse proxy and compromise the entire Appsmith deployment.

Teams running self-hosted Appsmith instances should upgrade to version 2.1 or later immediately. Any deployment exposed to untrusted authenticated users should be considered at risk, as exploitation requires only a valid low-privileged account. Refer to the vendor security advisory for full remediation details and interim mitigations.

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, a cross-platform style build system, is affected by a high-severity prototype pollution vulnerability with a CVSS score of 8.8. The flaw, present in versions 4.3.0 through 5.4.3, can be triggered through direct use of the convertTokenData function, the Expand API, or the standard transform lifecycle. A functional exploit exists, and impact is particularly severe when Style Dictionary is integrated into a Node.js server application, where prototype pollution can lead to denial of service or remote code execution.

Teams using Style Dictionary in server-side Node.js applications should upgrade to version 5.4.4 or later as a priority. Even teams using it solely as a build-time tool should update promptly, as the vulnerability surface spans multiple common usage patterns. Refer to the vendor commit for technical details and patch information.

Vendor Advisory

🟠 [HIGH] rclone/rclone

1 CVE | CVSS 3.1: 9.8 | AAS 11.1

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

Rclone, a widely used command-line tool for syncing files across cloud storage providers, is affected by a critical-severity vulnerability with a CVSS score of 9.8. In versions 1.46.0 through 1.74.2, the remote control daemon mode started with rcd –rc-serve accepts unauthenticated GET and HEAD requests that allow an attacker to inject inline remote configurations through crafted URL paths. These configurations can set backend options that execute arbitrary local commands during initialization, enabling unauthenticated remote code execution with a single HTTP request.

Any team running rclone in remote control daemon mode with –rc-serve should upgrade to version 1.74.3 or later immediately. Given the unauthenticated nature of this attack and the prevalence of rclone in automation pipelines, backup infrastructure, and cloud migration workflows, exposed instances should be considered at critical risk. Refer to the vendor security advisory for full details and interim mitigations.

Vendor Advisory

🟠 [HIGH] rocketchat/rocket.chat

6 CVEs | CVSS 4.0: 9.3 | AAS 10.7

  • cpe:2.3:a:rocketchat:rocket.chat:*:*:*:*:*:*:*:* (< 7.10.13)
  • cpe:2.3:a:rocketchat:rocket.chat:*:*:*:*:*:*:*:* (>= 8.0.0, < 8.0.7)
  • cpe:2.3:a:rocketchat:rocket.chat:*:*:*:*:*:*:*:* (>= 8.1.0, < 8.1.6)
  • cpe:2.3:a:rocketchat:rocket.chat:*:*:*:*:*:*:*:* (>= 8.2.0, < 8.2.6)
  • cpe:2.3:a:rocketchat:rocket.chat:*:*:*:*:*:*:*:* (>= 8.3.0, < 8.3.6)

Rocket.Chat, an open-source communications platform, is affected by six vulnerabilities, including multiple high-severity issues with a maximum CVSS score of 9.3. The lead vulnerability is an authentication bypass in the Apple OAuth login handler, where a missing email field in an Apple-issued JWT causes the application to fall back to accepting an arbitrary attacker-supplied email value from the request. This allows an attacker to forge authentication and gain access to any account on instances with Apple sign-in enabled.

Organizations running self-hosted Rocket.Chat instances should upgrade immediately to version 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13 depending on their release track. Instances with Apple OAuth enabled should be treated as highest priority, and administrators should review authentication logs for signs of unauthorized access. Refer to the vendor security advisory for complete details on all six issues.

Vendor Advisory

🟠 [HIGH] cacti/cacti

4 CVEs | CVSS 3.1: 9.8 | AAS 10.6

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

Cacti, an open-source network performance and fault management framework, is affected by four vulnerabilities, including multiple critical-severity issues with a maximum CVSS score of 9.8. The lead vulnerability is an unauthenticated local file inclusion flaw exploitable through the graph_theme parameter and weaknesses in rrdtool IPC serialization, allowing attackers to read sensitive files or potentially achieve code execution without any credentials. All versions through 1.2.30 are affected.

Organizations running Cacti for network monitoring should upgrade to version 1.2.31 immediately. Given the unauthenticated nature of the lead vulnerability and Cacti’s typical deployment on internal networks with access to sensitive infrastructure data, exploitation poses significant risk of lateral movement. Refer to the vendor commit for patch details on all four issues.

Vendor Advisory

🟠 [HIGH] tryghost/ghost

1 CVE | CVSS 3.1: 9.6 | AAS 10.4

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

Ghost, a Node.js-based content management system by TryGhost, is affected by a critical-severity cache poisoning vulnerability with a CVSS score of 9.6. An unauthenticated attacker can send a crafted x-ghost-preview header to alter the rendered frontend response, and when Ghost is deployed behind a shared caching layer, that manipulated response can be cached and served to all subsequent visitors requesting the same page. This enables widespread defacement or injection of malicious content without any authentication.

Organizations running Ghost behind shared caching infrastructure such as CDNs or reverse proxy caches should upgrade to version 6.37.0 or later immediately. Deployments without a shared caching layer are at reduced risk but should still update as a precaution. Refer to the vendor security advisory for full technical details and guidance on identifying affected cache configurations.

Vendor Advisory

🟠 [HIGH] feast-dev/feast

1 CVE | CVSS 4.0: 9.3 | AAS 9.7

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

Feast, an open-source feature store for machine learning by feast-dev, is affected by a critical-severity unsafe deserialization vulnerability with a CVSS score of 9.3. The registry server’s gRPC endpoint decodes the user_defined_function.body field from base64 and passes it directly to dill.loads() before performing any authorization checks, allowing an unauthenticated attacker to send a crafted request containing a malicious serialized Python object that executes arbitrary operating system commands on the server.

Teams running Feast registry servers should upgrade to version 0.63.0 or later immediately. Any exposed Feast gRPC endpoint running a prior version should be considered at critical risk of full system compromise, and network access to the registry server should be restricted as an interim mitigation. Refer to the vendor commit for complete patch details.

Vendor Advisory

🟠 [HIGH] getsentry/sentry

1 CVE | CVSS 3.1: 7.5 | AAS 9.3

  • cpe:2.3:a:getsentry:sentry:*:*:*:*:*:*:*:* (>= 24.4.0, < 26.5.2)

Sentry, an error tracking and performance monitoring platform by getsentry, is affected by a high-severity Regular Expression Denial of Service vulnerability with a CVSS score of 7.5. A regex in the event ingestion pipeline is applied to attacker-controlled fields on incoming events and can be crafted to consume disproportionate CPU time, allowing an unauthenticated attacker to degrade or deny service to the monitoring platform. Versions 24.4.0 through 26.5.1 are affected.

Organizations running self-hosted Sentry instances should upgrade to version 26.5.2 or later promptly. Since Sentry ingestion endpoints are typically exposed to application clients and potentially the internet, this denial of service risk is readily exploitable and could blind teams to production errors during an attack. Refer to the vendor pull request for patch details.

Vendor Advisory

🟠 [HIGH] lepture/mistune

1 CVE | CVSS 4.0: 8.7 | AAS 9.1

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

Mistune, a Python Markdown parser by lepture, is affected by a high-severity CPU exhaustion denial of service vulnerability with a CVSS score of 8.7. The parse_link_text function exhibits quadratic-time behavior when processing Markdown input containing many consecutive open bracket characters, as a regex search inside a loop repeatedly re-scans large portions of the remaining string. An attacker supplying crafted Markdown input to any application using Mistune can trigger sustained CPU exhaustion. All versions prior to 3.3.0 are affected.

Teams using Mistune as a dependency in web applications, APIs, or any service that processes user-supplied Markdown should upgrade to version 3.3.0 or later immediately. Given Mistune’s widespread use as a lightweight Markdown library across the Python ecosystem, teams should also audit their dependency trees for indirect usage. Refer to the vendor security advisory for full details.

Vendor Advisory

🟠 [HIGH] jellyfin/jellyfin

2 CVEs | CVSS 3.1: 8.8 | AAS 9.1

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

Jellyfin, an open-source self-hosted media server, is affected by two vulnerabilities, including at least one high-severity issue with a maximum CVSS score of 8.8. The lead vulnerability allows any authenticated non-admin user to exploit the POST /ClientLog/Document endpoint by injecting path traversal sequences into the unsanitized Client field of the Authorization header, enabling arbitrary file writes with attacker-controlled content to any path accessible by the Jellyfin service user. Versions 10.9.0 through 10.11.9 are affected.

Administrators running Jellyfin instances, particularly those with user registration enabled or shared with untrusted users, should upgrade to version 10.11.10 or later immediately. Arbitrary file write vulnerabilities of this nature can typically be escalated to remote code execution depending on the host environment. Refer to the vendor security advisory for full details on both issues.

Vendor Advisory

🟠 [HIGH] proftpd_project/proftpd

1 CVE | CVSS 4.0: 8.6 | AAS 9.1

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

ProFTPD, a widely deployed open-source FTP server, is affected by a high-severity access control bypass vulnerability with a CVSS score of 8.6. Authenticated FTP users can circumvent Directory ACL restrictions, including DenyAll-protected directories, by prefixing paths with /proc/self/root in the RNFR command handler. This causes the path canonicalization logic to bypass lexical comparisons against configured Directory blocks, enabling attackers to rename and subsequently retrieve files from otherwise restricted locations. Versions through 1.3.9b and 1.3.10rc2 are affected.

Organizations running ProFTPD on Linux systems should monitor the vendor site for a patched release and apply it as soon as available. As an interim measure, administrators should restrict FTP user access to the minimum necessary directories and audit file rename activity for suspicious /proc/self/root path patterns. Refer to the vendor advisory for further guidance.

Vendor Advisory