17 vulnerabilities across 15 products scored HIGH or above on July 16, 2026.

  • 🟠 HIGH: 17

Exploit Status Upgrades

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

  • [UPGRADED] CVE-2026-57219 (rabbitmq/rabbitmq_server) — F1: theoretical → itw, AAS: 10.9 → 13.7 (HIGH → CRITICAL). Originally in 2026-07-10 bulletin.
  • [UPGRADED] CVE-2026-55884 (tilt-dev/tilt) — F1: exploitable → itw, AAS: 10.3 → 13.0 (HIGH → CRITICAL). Originally in 2026-07-10 bulletin.
  • [UPGRADED] CVE-2026-55879 (openreplay/openreplay) — F1: exploitable → itw, AAS: 10.3 → 13.3 (HIGH → CRITICAL). Originally in 2026-07-10 bulletin.
  • [UPGRADED] CVE-2026-54003 (getkirby/kirby) — F1: theoretical → poc, AAS: 11.8 → 11.5 (HIGH → HIGH). Originally in 2026-07-09 bulletin.
  • [UPGRADED] CVE-2026-59827 (metabase/metabase) — F1: exploitable → itw, AAS: 11.2 → 13.1 (HIGH → CRITICAL). Originally in 2026-07-09 bulletin.
  • [UPGRADED] CVE-2026-59148 (mockoon/mockoon) — F1: exploitable → itw, AAS: 9.6 → 12.6 (HIGH → CRITICAL). Originally in 2026-07-09 bulletin.
  • [UPGRADED] CVE-2026-59858 (vim/vim) — F1: exploitable → itw, AAS: 9.3 → 12.3 (HIGH → CRITICAL). Originally in 2026-07-09 bulletin.
  • [UPGRADED] CVE-2026-55207 (pimcore/pimcore) — F1: theoretical → poc, AAS: 9.1 → 11.6 (HIGH → HIGH). Originally in 2026-07-09 bulletin.

🟠 [HIGH] kopia/kopia

1 CVE | CVSS 3.1: 9.8 | AAS 11.1

  • cpe:2.3:a:kopia:kopia:*:*:*:*:*:*:*:* (< 0.23.0)

Kopia, a cross-platform backup tool for Windows, macOS, and Linux, is affected by a critical remote code execution vulnerability (CVE-2026-45695, CVSS 9.8). When the Kopia HTTP server is started with the –without-password flag, unauthenticated attackers can supply crafted SFTP storage configuration via the repository API that triggers arbitrary command execution through SSH ProxyCommand injection. This vulnerability is exploitable and requires no authentication.

Organizations running Kopia’s HTTP server in passwordless mode should immediately upgrade to version 0.23.0 or later. Security teams managing backup infrastructure should audit deployments for exposed Kopia server instances and ensure no instances are running with the –without-password option until patching is complete.

Vendor Advisory

🟠 [HIGH] pheditor/pheditor

1 CVE | CVSS 3.1: 9.8 | AAS 10.9

  • cpe:2.3:a:pheditor:pheditor:*:*:*:*:*:*:*:*

Pheditor, a PHP-based file editor and terminal tool, is affected by a critical default credentials vulnerability (CVE-2026-55579, CVSS 9.8). The application ships with a hardcoded default password of “admin” and provides no mechanism to force a password change on first login, allowing unauthenticated attackers to gain full access to file editing, file upload, and built-in terminal features, resulting in arbitrary file read/write and remote code execution.

Anyone deploying Pheditor should immediately change the default password, restrict network access to the application, and monitor for signs of unauthorized access. Given the trivial exploitability and severity, any internet-exposed instance running default credentials should be considered compromised.

Vendor Advisory

🟠 [HIGH] envoyproxy/envoyproxy/gateway

1 CVE | CVSS 3.1: 9.1 | AAS 10.5

  • cpe:2.3:a:github.com:envoyproxy_gateway:*:*:*:*:*:*:*:* (>= 1.2.0, < 1.2.7)
  • cpe:2.3:a:github.com:envoyproxy_gateway:*:*:*:*:*:*:*:* (>= 1.3.0, < 1.3.1)

Envoy Gateway (envoyproxy/gateway) is affected by a path traversal vulnerability (CVE-2026-53713, CVSS 9.1) in its Lua-based security validation logic. The path normalization function fails to collapse redundant path separators, allowing malicious Lua code submitted via an EnvoyExtensionPolicy to bypass critical path restrictions and read arbitrary files from the gateway controller pod’s filesystem, even under the default Strict validation mode.

Teams running Envoy Gateway in Kubernetes environments should review their deployments for exposure and apply the vendor patch promptly. Until patched, operators should restrict who can create or modify EnvoyExtensionPolicy resources and monitor for unusual file access patterns within gateway controller pods.

Vendor Advisory

🟠 [HIGH] openziti/zrok

1 CVE | CVSS 4.0: 9.9 | AAS 10.3

  • cpe:2.3:a:openziti:zrok:*:*:*:*:*:*:*:*

zrok, an OpenZiti-based tool for sharing web services, files, and network resources, is affected by a server-side request forgery vulnerability (CVE-2026-45568, CVSS 9.9). The Python SDK’s ProxyShare Flask proxy route accepts absolute URLs in the request path that override the configured target host, allowing attackers to force the server to make requests to arbitrary attacker-controlled URLs and return their responses.

Organizations using zrok’s Python SDK with ProxyShare functionality should upgrade to version 2.0.3 immediately. This vulnerability is exploitable and could allow attackers to access internal services, exfiltrate data, or pivot within protected networks through the proxy.

Vendor Advisory

🟠 [HIGH] wwbn/avideo

1 CVE | CVSS 4.0: 9.2 | AAS 10.2

  • cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*

AVideo, an open-source video platform, through version 29.0 is affected by an OS command injection vulnerability (CVE-2026-63304, CVSS 9.2). The listFFmpegProcesses() function in the API plugin fails to sanitize keyword parameters interpolated into shell commands, allowing attackers who can craft a valid encrypted payload to break out of the quoting context and execute arbitrary commands as the web server user.

Organizations hosting AVideo instances should apply the vendor patch immediately and audit logs for signs of exploitation. Until patched, restricting access to the standalone API endpoint and monitoring for unusual process execution under the web server user are recommended mitigations.

Vendor Advisory

🟠 [HIGH] avwo/whistle

1 CVE | CVSS 4.0: 8.7 | AAS 10.1

  • cpe:2.3:a:avwo:whistle:*:*:*:*:*:*:*:*

Whistle, an HTTP/HTTPS/WebSocket debugging proxy, prior to version 2.10.3 is affected by an arbitrary file read vulnerability (CVE-2026-55629, CVSS 8.7). The temp file retrieval endpoint fails to properly restrict filenames that do not match the expected temporary file pattern, allowing remote attackers to supply crafted path values and read arbitrary files from the host system, including sensitive files such as /etc/passwd.

Development and security teams using Whistle as a debugging proxy should upgrade to version 2.10.3 immediately. Any Whistle instance exposed to untrusted networks should be considered at risk, and operators should verify that no sensitive data has been exfiltrated prior to patching.

Vendor Advisory

🟠 [HIGH] timwhitlock/loco_translate

1 CVE | CVSS 3.1: 8.8 | AAS 10.1

  • cpe:2.3:a:timwhitlock:loco_translate:*:*:*:*:*:*:*:* (< 2.8.6)

Loco Translate, a popular WordPress translation management plugin, in all versions up to and including 2.8.5 is affected by a cross-site request forgery vulnerability (CVE-2026-15005, CVSS 8.8) that enables remote code execution. Missing nonce validation on the execTemplate function allows unauthenticated attackers to trick an authenticated administrator into executing arbitrary PHP code on the server by exploiting a php://filter stream wrapper bypass in the template include path.

WordPress site administrators using Loco Translate should update beyond version 2.8.5 immediately. Given the widespread use of this plugin and the ability to achieve full server compromise through a single forged request, this should be treated as a high-priority patch for any WordPress environment.

Vendor Advisory

🟠 [HIGH] cyberlord92/saml_single_sign_on_–_sso_login

1 CVE | CVSS 3.1: 9.8 | AAS 10.1

  • cpe:2.3:a:cyberlord92:saml_single_sign_on_sso_login:*:*:*:*:*:*:*:* (< 5.4.4)

The SAML Single Sign On – SSO Login plugin for WordPress, in all versions up to and including 5.4.3, is affected by a critical authentication bypass vulnerability (CVE-2026-15013, CVSS 9.8). The plugin reads the signature algorithm directly from the attacker-controlled SAMLResponse rather than enforcing the locally configured algorithm, enabling a signature algorithm confusion attack that recasts the IdP’s RSA public key as an HMAC shared secret, allowing unauthenticated attackers to forge valid SAML assertions and log in as any user including administrators.

Any WordPress site relying on this plugin for SAML-based single sign-on should update beyond version 5.4.3 immediately and audit authentication logs for suspicious logins. This is a network-exploitable, unauthenticated full authentication bypass that requires no user interaction, making it an urgent priority for all affected environments.

Vendor Advisory

🟠 [HIGH] illumos/illumos-gate

1 CVE | CVSS 4.0: 9.1 | AAS 10.0

  • cpe:2.3:a:illumos:illumos-gate:*:*:*:*:*:*:*:*

illumos-gate, the core OS kernel for illumos-based distributions, is affected by a critical kernel heap corruption vulnerability in the SCTP network stack (CVE-2026-15422, CVSS 9.1). The SCTP inbound path performs association lookup on INIT ACK chunks without properly validating address parameters, and because this occurs before integrity checks or IPsec policy are applied, a remote unauthenticated attacker can send a crafted packet to trigger out-of-bounds access and potentially achieve remote code execution at the kernel level.

Organizations running illumos-based systems such as OmniOS, SmartOS, or OpenIndiana with SCTP-capable network interfaces should apply the vendor patch immediately. Until patched, filtering SCTP traffic at the network perimeter where it is not explicitly required is a recommended mitigation to reduce exposure.

Vendor Advisory

🟠 [HIGH] argoproj/argo-workflows

1 CVE | CVSS 4.0: 8.9 | AAS 9.8

  • cpe:2.3:a:argoproj:argo-workflows:*:*:*:*:*:*:*:*

Argo Workflows, a container-native workflow engine for Kubernetes, prior to versions 3.7.15 and 4.0.6 is affected by a privilege escalation vulnerability (CVE-2026-54526, CVSS 8.9) that bypasses the incomplete allow-list fix for CVE-2026-31892. The ArtifactGC field is allow-listed wholesale, but its PodSpecPatch sub-field flows unvalidated into pod specifications, allowing workflow submitters to inject arbitrary pod-level configurations and escape intended security constraints.

Organizations running Argo Workflows on Kubernetes should upgrade to version 3.7.15 or 4.0.6 immediately, particularly in multi-tenant environments where untrusted users can submit workflows. Until patched, restricting workflow submission privileges and auditing existing workflows for suspicious ArtifactGC configurations are recommended mitigations.

Vendor Advisory

🟠 [HIGH] grafana-cold-storage/oncall

1 CVE | CVSS 4.0: 9.3 | AAS 9.7

  • cpe:2.3:a:grafana-cold-storage:oncall:*:*:*:*:*:*:*:*

Grafana OnCall through version 1.16.11 is affected by a critical unauthenticated access vulnerability (CVE-2026-63087, CVSS 9.3) that allows remote attackers to obtain a valid PluginAuthToken using hardcoded default stack and org identifiers present in the public source tree. With this token, attackers can authenticate against all internal API endpoints, create arbitrary admin users, revoke legitimate plugin tokens, and achieve full takeover of the OnCall instance.

Organizations running Grafana OnCall should upgrade beyond version 1.16.11 immediately and audit for unauthorized admin accounts or token revocations that may indicate prior exploitation. Any internet-exposed instance running default configuration values should be considered at high risk, and operators should rotate all credentials and verify plugin token integrity after patching.

Vendor Advisory

🟠 [HIGH] stoatchat/stoatchat

1 CVE | CVSS 4.0: 9.2 | AAS 9.6

  • cpe:2.3:a:stoatchat:stoatchat:*:*:*:*:*:*:*:* (< 0.13.5)

stoatchat, an open-source chat application, prior to version 0.13.5 is affected by an unauthenticated server-side request forgery vulnerability (CVE-2026-63306, CVSS 9.2) in its /proxy and /embed endpoints. These endpoints accept arbitrary URLs without DNS resolution filtering or private IP range validation, allowing remote attackers to enumerate internal services, fingerprint applications, and access cloud instance metadata endpoints through direct requests or redirect chains.

Organizations running stoatchat should upgrade to version 0.13.5 immediately, especially instances deployed in cloud environments where metadata endpoints could expose credentials. Until patched, restricting network access to the /proxy and /embed endpoints or placing the application behind a firewall that blocks outbound requests to internal ranges is strongly recommended.

Vendor Advisory

🟠 [HIGH] getkirby/kirby

3 CVEs | CVSS 4.0: 8.8 | AAS 9.5

  • cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:*

Kirby CMS versions 5.3.0 through 5.4.0 is affected by 3 vulnerabilities including multiple exploitable issues (max CVSS 8.8), with the lead vulnerability being a path traversal flaw in user ID validation that was introduced by a lazy-loading performance optimization. The insufficient validation allows unauthenticated attackers to manipulate user IDs to traverse the filesystem via the authentication API, potentially accessing or manipulating data outside the intended account directories.

Organizations running Kirby CMS version 5.3.0 or later should upgrade to version 5.4.1 immediately. Given that the authentication API is accessible without prior authentication, internet-facing Kirby installations are directly exposed and should be prioritized for patching.

Vendor Advisory

🟠 [HIGH] wg-easy/wg-easy

1 CVE | CVSS 4.0: 9.0 | AAS 9.3

  • cpe:2.3:a:wg-easy:wg-easy:*:*:*:*:*:*:*:*

WireGuard Easy (wg-easy) through version 15.3.0 is affected by a critical weak token generation vulnerability (CVE-2026-63089, CVSS 9.0) in its one-time link mechanism for distributing WireGuard peer credentials. The token is derived from CRC32 over a random value constrained to 0-999, creating a keyspace of at most 1,000 candidates per client ID that can be brute-forced against the unauthenticated /cnf/:oneTimeLink route, which lacks rate limiting.

Organizations using wg-easy to manage WireGuard deployments should apply commit 66b292b or update to the latest version immediately, as successful exploitation allows unauthenticated attackers to recover VPN peer credentials. Any previously generated one-time links should be considered compromised, and administrators should regenerate peer configurations after patching.

Vendor Advisory

🟠 [HIGH] microsoft/prompty

1 CVE | CVSS 4.0: 8.7 | AAS 9.1

  • cpe:2.3:a:microsoft:prompty:*:*:*:*:*:*:*:* (>= 2.0.0-alpha.1, < 2.0.0-beta.3)

Microsoft Prompty, a markdown-based file format and toolchain for LLM prompts, from version 2.0.0-alpha.1 until 2.0.0-beta.3 is affected by an arbitrary code execution vulnerability (CVE-2026-53597, CVSS 8.7) in its TypeScript loader. The @prompty/core package uses the gray-matter library without disabling executable JavaScript frontmatter engines, allowing an attacker who can supply a crafted .prompty file to execute arbitrary JavaScript during prompt loading.

Teams using Prompty’s TypeScript SDK in AI/ML pipelines should upgrade to version 2.0.0-beta.3 immediately. Any workflow that loads .prompty files from untrusted sources, shared repositories, or user-supplied inputs is directly exploitable, and organizations should audit prompt file sources and review for suspicious frontmatter content.

Vendor Advisory