40 vulnerabilities across 15 products scored HIGH or above on August 10, 2026.

  • 🔴 CRITICAL: 9
  • 🟠 HIGH: 31

Exploit Status Upgrades

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

  • [UPGRADED] CVE-2026-71558 (apache/fory) — F1: exploitable → functional, AAS: 10.9 → 12.9 (HIGH → CRITICAL). Originally in 2026-08-07 bulletin.
  • [UPGRADED] CVE-2026-62873 (microsoft/microsoft_365_admin_center) — F1: theoretical → poc, AAS: 9.1 → 11.6 (HIGH → HIGH). Originally in 2026-08-07 bulletin.
  • [UPGRADED] CVE-2026-65507 (sergey/aiwu) — F1: exploitable → functional, AAS: 10.9 → 12.9 (HIGH → CRITICAL). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2026-5430 (wso2/api_control_plane) — F1: theoretical → poc, AAS: 10.7 → 13.2 (HIGH → CRITICAL). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2026-34191 (apache/apr-util) — F1: exploitable → functional, AAS: 10.5 → 13.7 (HIGH → CRITICAL). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2026-28139 (wpdreams/ajax_search_lite) — F1: exploitable → functional, AAS: 10.1 → 12.1 (HIGH → CRITICAL). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2025-15039 (wso2/wso2_identity_server) — F1: theoretical → itw, AAS: 9.9 → 13.9 (HIGH → CRITICAL). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2026-65583 (apache/cxf) — F1: exploitable → functional, AAS: 9.9 → 11.9 (HIGH → HIGH). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2026-68079 (apache/cxf) — F1: theoretical → poc, AAS: 9.6 → 12.1 (HIGH → CRITICAL). Originally in 2026-08-06 bulletin.
  • [UPGRADED] CVE-2026-48168 (mervinpraison/praisonai) — F1: exploitable → functional, AAS: 10.8 → 12.8 (HIGH → CRITICAL). Originally in 2026-08-05 bulletin.
  • [UPGRADED] CVE-2026-70478 (flowiseai/flowise) — F1: theoretical → poc, AAS: 9.9 → 12.4 (HIGH → CRITICAL). Originally in 2026-08-04 bulletin.
  • [UPGRADED] CVE-2026-39931 (openemr/openemr) — F1: exploitable → functional, AAS: 9.1 → 11.1 (HIGH → HIGH). Originally in 2026-08-03 bulletin.
  • [UPGRADED] CVE-2026-38447 (osticket/osticket) — F1: theoretical → poc, AAS: 9.6 → 12.1 (HIGH → CRITICAL). Originally in 2026-08-03 bulletin.
  • [UPGRADED] CVE-2026-46713 (misskey-dev/misskey) — F1: theoretical → poc, AAS: 9.1 → 11.6 (HIGH → HIGH). Originally in 2026-08-03 bulletin.

🔴 [CRITICAL] metabase/metabase

2 CVEs | CVSS 4.0: 10.0 | AAS 12.9

  • cpe:2.3:a:metabase:metabase:*:*:*:*:*:*:*:*

Metabase, the popular open-source business intelligence and analytics platform, is affected by 2 critical vulnerabilities including at least one that allows unauthenticated SQL injection through publicly shared cards or dashboards exposing field-filter parameters. With a maximum CVSS 4.0 score of 10.0 and proof-of-concept exploit code available, this poses an immediate risk to any organization running Metabase instances, particularly those with publicly shared dashboards or embedded analytics.

Security teams should treat this as an emergency priority. Review the vendor advisory at the linked GitHub security page, identify all Metabase deployments in your environment, and apply the latest patches immediately. As a temporary mitigation, consider disabling or restricting public sharing and embedded dashboard features until patching is complete.

Vendor Advisory

🔴 [CRITICAL] tencent/apijson

1 CVE | CVSS 3.1: 9.8 | AAS 12.6

  • cpe:2.3:a:tencent:apijson:*:*:*:*:*:*:*:*

Tencent APIJSON through version 8.1.8, an open-source framework for building RESTful APIs without writing backend code, contains a critical SQL injection vulnerability that allows unauthenticated remote attackers to bypass per-table access control and read arbitrary database tables by abusing the Map-form @having operator. With a CVSS 3.1 score of 9.8 and proof-of-concept exploit code publicly available, any organization exposing APIJSON-based services is at significant risk of unauthorized data access.

Teams running APIJSON should immediately check their deployed version, monitor the vendor’s GitHub repository for a patched release, and consider applying input validation or WAF rules to filter malicious @having parameters as an interim mitigation until an official fix is available.

Vendor Advisory

🔴 [CRITICAL] firecrawl/firecrawl

1 CVE | CVSS 4.0: 9.3 | AAS 12.2

  • cpe:2.3:a:firecrawl:firecrawl:*:*:*:*:*:*:*:*

Firecrawl, a widely used tool for converting websites into LLM-ready markdown and structured data, contains a critical arbitrary file read vulnerability in versions prior to 2.11.32. The flaw exists in the extraction functionality’s JSON schema dereferencing logic, where unsafe default resolver settings allow an authenticated attacker to resolve external and local file references during schema processing, potentially exposing sensitive server-side files such as credentials and configuration data. With a CVSS 4.0 score of 9.3 and proof-of-concept exploit code available, this is a high-priority issue for any organization running self-hosted Firecrawl instances.

Teams should upgrade to Firecrawl version 2.11.32 or later immediately, referencing the vendor’s fix commit linked in the advisory for technical details.

Vendor Advisory

🔴 [CRITICAL] spip/spip

1 CVE | CVSS 4.0: 7.7 | AAS 12.2

  • cpe:2.3:a:spip:spip:*:*:*:*:*:*:*:*

SPIP, the open-source content management system, contains a critical code injection vulnerability in versions prior to 4.4.18 that affects installations using SQLite as their database backend. An authenticated attacker with editor-level privileges or higher can exploit improper handling of array-typed input in the navigation menu endpoint to break out of a quoted string context and execute arbitrary OS commands on the web server, requiring only a single crafted GET request. A functional exploit is publicly available, making active exploitation highly likely.

Organizations running SPIP with SQLite backends should upgrade to version 4.4.18 immediately. MySQL-backed installations are not affected, but upgrading across all deployments is strongly recommended as a precaution. Refer to the vendor’s security advisory for full details.

Vendor Advisory

🔴 [CRITICAL] dokploy/dokploy

23 CVEs | CVSS 3.1: 9.9 | AAS 12.1

  • cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* (>= 0.29.3, < 0.29.13)
  • cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* (>= 0.29.2, < 0.29.13)
  • cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* (< 0.29.9)

Dokploy, a free self-hostable Platform as a Service (PaaS), is affected by 23 vulnerabilities in versions prior to 0.29.13, including multiple critical command injection flaws with a maximum CVSS 3.1 score of 9.9. The lead vulnerability allows authenticated users to inject arbitrary shell commands through unsanitized database name and backup file parameters used in restore pipelines, and functional exploit code is publicly available for at least one of these issues. The breadth and severity of this disclosure suggest systemic input validation failures across multiple Dokploy components.

Any organization self-hosting Dokploy should upgrade to version 0.29.13 or later immediately and audit logs for any suspicious backup or restore activity. Until patching is complete, restrict access to the Dokploy management interface to trusted administrators only.

Vendor Advisory

🟠 [HIGH] fosrl/pangolin

1 CVE | CVSS 3.1: 9.6 | AAS 11.9

  • cpe:2.3:a:fosrl:pangolin:*:*:*:*:*:*:*:*

Pangolin, a self-hosted tunneled reverse proxy by fosrl used for exposing internal services, contains a critical improper authorization vulnerability in versions through 1.20.0 that allows an authenticated remote attacker to reuse an access token issued for one resource to gain unauthorized access to any resource across any organization on the same deployment. With a CVSS 3.1 score of 9.6 and proof-of-concept exploit code available, this flaw effectively breaks all cross-resource and cross-organization access boundaries, making it a severe multi-tenant isolation failure.

Organizations running Pangolin should monitor the vendor’s GitHub repository for a patched release and upgrade as soon as one is available. In the interim, review access logs for signs of cross-resource token reuse and consider restricting external access to the Pangolin instance until a fix is applied.

Vendor Advisory

🟠 [HIGH] flowiseai/flowise

1 CVE | CVSS 4.0: 8.7 | AAS 11.6

  • cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:* (>= 2.2.4)

Flowise, a popular open-source drag-and-drop tool for building LLM application workflows, contains a missing authorization vulnerability in versions 2.2.4 through 3.1.4 that allows unauthenticated attackers to download private files from any chatflow on the instance. The file download endpoint was improperly added to the global authentication whitelist, completely bypassing session and API key verification, and proof-of-concept exploit code is publicly available. Any organization running an internet-exposed Flowise instance is at risk of unauthorized access to sensitive uploaded files across all chatflows.

Teams should note that the vendor advisory links to a sunset notice, indicating Flowise may be end-of-life. Organizations should check for an available patch, restrict network access to Flowise instances immediately, and evaluate migration to a supported alternative if no fix is forthcoming.

Vendor Advisory

🟠 [HIGH] frappe/erpnext

1 CVE | CVSS 3.1: 9.9 | AAS 11.6

  • cpe:2.3:a:frappe:erpnext:*:*:*:*:*:*:*:* (< 15.118.0)
  • cpe:2.3:a:frappe:erpnext:*:*:*:*:*:*:*:* (>= 16.0.0, < 16.29.0)

ERPNext, a widely used open-source Enterprise Resource Planning platform by Frappe, contains a critical server-side template injection vulnerability in versions prior to 15.118.0 and 16.29.0. An authenticated user with a common operational role can inject malicious template expressions into the subject, body, or pdf_name fields of the Statement of Accounts processing module, achieving arbitrary server-side code execution and cross-tenant data access through unrestricted template globals. With a CVSS 3.1 score of 9.9 and proof-of-concept exploit code available, this vulnerability is particularly dangerous given that exploitation requires only routine user privileges rather than administrative access.

Organizations running ERPNext should upgrade to version 15.118.0 or 16.29.0 immediately and audit logs for any unusual activity in the Statement of Accounts module.

Vendor Advisory

🟠 [HIGH] alseambusher/crontab-ui

2 CVEs | CVSS 3.1: 9.8 | AAS 11.4

  • cpe:2.3:a:alseambusher:crontab-ui:*:*:*:*:*:*:*:*

Crontab UI, an open-source web-based interface for managing cron jobs by alseambusher, is affected by 2 critical vulnerabilities in versions through 0.4.2, including multiple OS command injection flaws. The lead vulnerability allows an unauthenticated remote attacker to inject arbitrary cron job entries by sending a crafted GET request with URL-encoded newlines in the env_vars parameter, effectively granting persistent command execution on the host system. With a maximum CVSS 3.1 score of 9.8 and proof-of-concept exploit code available, any internet-exposed instance is at immediate risk of full system compromise.

Organizations should check for Crontab UI deployments, restrict network access to trusted hosts immediately, and monitor the vendor’s GitHub repository for a patched release. Given the project’s maintenance status, teams should evaluate migrating to an actively supported alternative.

Vendor Advisory

🟠 [HIGH] daptin/daptin

1 CVE | CVSS 3.1: 9.1 | AAS 11.4

  • cpe:2.3:a:daptin:daptin:*:*:*:*:*:*:*:*

Daptin, an open-source headless CMS and API server, contains a critical improper authorization vulnerability in versions through 0.12.34 that allows unauthenticated remote attackers to read, create, update, and delete usergroup records. The flaw exists because permission check functions fail to reject null or zero user ID references, effectively granting full CRUD access to unauthenticated requests, while only the execute permission path includes the proper guard. With a CVSS 3.1 score of 9.1 and proof-of-concept exploit code available, any exposed Daptin instance is at risk of complete access control bypass and unauthorized data manipulation.

Organizations running Daptin should immediately restrict network access to the service and monitor the vendor’s GitHub repository for a patched release. Given the severity, consider taking publicly exposed instances offline until a fix is confirmed.

Vendor Advisory

🟠 [HIGH] eugeny/tabby

1 CVE | CVSS 3.1: 8.1 | AAS 11.4

  • cpe:2.3:a:eugeny:tabby:*:*:*:*:*:*:*:*

Tabby (formerly Terminus), a popular cross-platform terminal emulator, contains a path traversal vulnerability in versions prior to 1.0.235 that can be exploited by a malicious SFTP server. When a user downloads a folder via SFTP, the server can supply filenames containing backslash traversal sequences that bypass POSIX path processing, allowing arbitrary file writes to locations outside the intended download directory on the user’s local system. With a CVSS 3.1 score of 8.1 and proof-of-concept exploit code available, this is a significant risk for developers and system administrators who use Tabby to connect to untrusted or compromised SSH servers.

Users should upgrade to Tabby version 1.0.235 or later immediately and exercise caution when connecting to unfamiliar SFTP servers until the update is applied.

Vendor Advisory

🟠 [HIGH] lobehub/lobe-chat

1 CVE | CVSS 3.1: 7.6 | AAS 10.9

  • cpe:2.3:a:lobehub:lobe-chat:*:*:*:*:*:*:*:*

LobeChat, an open-source AI chat framework by LobeHub, contains a stored cross-site scripting vulnerability in versions through 2.2.13 that allows a low-privileged authenticated user to inject arbitrary JavaScript by uploading a crafted SVG file as their user avatar. Because the malicious payload is stored and rendered to other users viewing the attacker’s avatar, this can lead to session hijacking, credential theft, or further account compromise across the deployment. Proof-of-concept exploit code is publicly available.

Organizations running self-hosted LobeChat instances should monitor the vendor’s GitHub repository for a patched release and upgrade promptly. As an interim measure, consider restricting SVG uploads or implementing server-side content sanitization for user-uploaded image files.

Vendor Advisory

🟠 [HIGH] zephyrproject/zephyr

1 CVE | CVSS 3.1: 8.4 | AAS 10.7

  • cpe:2.3:a:zephyrproject:zephyr:*:*:*:*:*:*:*:*

Zephyr, the widely used open-source real-time operating system for IoT and embedded devices, contains a buffer overflow vulnerability in its DTLS Connection ID handling within the TLS sockets subsystem. The getsockopt handler for TLS_DTLS_PEER_CID_VALUE passes a caller-supplied buffer directly to mbedtls_ssl_get_peer_cid without verifying it meets the minimum required size, allowing a copy of up to 32 bytes of peer-negotiated CID data to overflow an undersized buffer and potentially enable code execution or memory corruption. With a CVSS 3.1 score of 8.4 and proof-of-concept exploit code available, this is a significant concern for any product using Zephyr’s DTLS stack.

Teams developing or deploying Zephyr-based firmware should apply the vendor’s fix commit and rebuild affected images promptly, particularly for any devices using DTLS with Connection ID support.

Vendor Advisory

🟠 [HIGH] cachethq/cachet

1 CVE | CVSS 4.0: 8.7 | AAS 10.6

  • cpe:2.3:a:cachethq:cachet:*:*:*:*:*:*:*:* (< 2.4.2)

Cachet, an open-source status page system, contains a server-side template injection vulnerability in versions through 2.4.1 that allows authenticated users to execute arbitrary PHP code on the server. By crafting malicious incident templates with Blade directives or Twig filters, an attacker can achieve remote code execution as the web server process whenever an incident is created using the poisoned template. Proof-of-concept exploit code is publicly available.

Organizations running Cachet should immediately restrict who can create or edit incident templates to only highly trusted administrators and monitor the vendor’s GitHub issue tracker for a patched release. Given Cachet’s limited maintenance activity, teams should evaluate whether migration to an actively supported status page platform is warranted.

Vendor Advisory

🟠 [HIGH] dulldusk/phpfm

2 CVEs | CVSS 3.1: 9.8 | AAS 10.6

  • cpe:2.3:a:dulldusk:phpfm:*:*:*:*:*:*:*:*

phpFM, a PHP-based web file manager by dulldusk, is affected by 2 critical vulnerabilities in versions through 1.8.0, including multiple issues that allow unauthenticated remote attackers to access full file manager functionality. The lead vulnerability is a complete absence of authentication, enabling any remote attacker to read, write, delete, and upload files anywhere on the server filesystem without credentials. With a maximum CVSS 3.1 score of 9.8 and proof-of-concept exploit code available, any internet-exposed phpFM instance is trivially exploitable for full server compromise.

Organizations should immediately take any phpFM installations offline or block access at the network level. Given the severity and the project’s maintenance status, teams should treat any exposed instance as potentially already compromised and migrate to an actively maintained file management solution.

Vendor Advisory