Executive assessment
Today's brief leads with Multiple vulnerabilities in SiYuan. All 15 selected findings retain their own technical scope, action, observed status, and evidence limits.
Panel synthesis: Finding 05 leads because it is a critical unauthenticated SSRF with proof-of-concept exploitation and no listed fix, so the immediate emphasis is compensating controls around proxy origins and outbound reachability. Finding 04 is a close alternative lead because it is also critical, PoC-backed, and affects authentication bypass on a management interface. Themes: Unauthenticated exposure; Server-side request forgery; PoC-backed flaws without listed fixes. Patch order: Finding 05 (Critical unauthenticated SSRF with proof-of-concept exploitation and no listed fix); Finding 04 (Critical OAuth authentication bypass with proof-of-concept exploitation and no listed fix); Finding 06 (Critical unauthenticated API exposure across four endpoints with proof-of-concept exploitation and no listed fix); Finding 03 (Critical missing authentication vulnerability with a stated fix in Nango 0.71.6 or later); Finding 07 (High-severity unauthenticated SSRF with proof-of-concept exploitation and a stated fix in OpenPanel 2.3.0).
Finding 01 — Multiple vulnerabilities in SiYuan
What changed: CVE coverage: CVE-2026-72799, CVE-2026-72798, CVE-2026-72797, CVE-2026-72796, CVE-2026-72794, CVE-2026-72795, CVE-2026-72793, CVE-2026-72792. The cited advisories disclose: Missing publish-access filter on the HPath/path-resolution endpoints discloses the private document tree to anonymous readers; Publish-access filter on renderAttributeView leaves related-database content unfiltered and fails open on non-block first columns; getEncryptedNotebookStatus discloses names and current lock/unlock state of all encrypted notebooks to anonymous readers; Static-file routes bypass the publish-access controls enforced on the REST API, exposing templates, snippets and export artifacts to anonymous readers; The session-cookie signing key is returned to anonymous readers by /api/system/getConf; Embedded block content is returned without publish-access filtering, leaking private and password-protected document content to anonymous readers; Non-administrator responses from /api/system/getConf omit three secrets that the configuration-export path explicitly strips, disclosing the session-cookie signing key and the OS username to anonymous readers; Tag labels from password-protected documents are returned to readers who have not entered the password.
Technical evidence: CVE-2026-72798; CVSS v4.0 9.2; weakness CWE-862; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-72798 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: github.com](https://github.com/advisories/GHSA-5w7r-f4cg-rqq7)
Finding 02 — USN-8732-1: Minetest vulnerability
What changed: It was discovered that Minetest did not properly sanitize the Lua sandbox environment when using LuaJIT. A malicious mod could escape the sandbox to execute arbitrary code and gain full file system access on the server.
Technical evidence: CVE-2026-41196; CVSS v4.0 9; weakness CWE-94; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-41196 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: ubuntu.com](https://ubuntu.com/security/notices/USN-8732-1)
Finding 03 — Nango: Missing Authentication for Critical Function
What changed: Nango before 0.71.6 contains a missing authentication vulnerability in the runner tRPC server that allows unauthenticated attackers to execute arbitrary JavaScript code by invoking the exposed start procedure without credentials. Attackers with network access to the runner port can send requests to the unauthenticated start procedure, bypassing the unenforced RUNNER_SECRET_KEY environment variable, to achieve remote code execution within the runner process.
Technical evidence: CVE-2026-9317; CVSS v4.0 9.2; weakness CWE-306; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Analyst note: Restrict network access to the runner port to trusted internal subnets, apply strict firewall rules, and ensure no public-facing load balancer exposes the runner port. ([ionix.io](https://www.ionix.io/threat-center/cve-2026-9317/), [vulncheck.com](https://www.vulncheck.com/advisories/nango-missing-authentication-rce-via-runner-trpc-server))
Affected: Nango versions before 0.71.6. ([vulncheck.com](https://www.vulncheck.com/advisories/nango-missing-authentication-rce-via-runner-trpc-server))
Fix: Nango 0.71.6 or later. ([ionix.io](https://www.ionix.io/threat-center/cve-2026-9317/))
Action: Map CVE-2026-9317 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-9317)
Finding 04 — Coolify: Improper Authentication
What changed: Coolify through 4.3.17 contains an authentication bypass vulnerability in the OAuth callback handler that signs users into existing accounts based solely on email address without verifying provider assertions or binding OAuth identities. Attackers can register a victim's email address on any enabled OAuth provider to obtain authenticated sessions as that user, bypassing password requirements and two-factor authentication.
Technical evidence: CVE-2026-86117; CVSS v4.0 9.2; weakness CWE-287; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Disable OAuth login providers until patched. Restrict network access to the Coolify management interface to trusted IPs or a VPN, and review audit logs for OAuth callback activity from unfamiliar sources. ([ionix.io](https://www.ionix.io/threat-center/cve-2026-86117/), [vulncheck.com](https://www.vulncheck.com/advisories/coolify-through-4.3.17-oauth-account-takeover-via-unverified-email-matching), [github.com](https://github.com/geo-chen/oss/blob/main/coolify.md))
Action: Map CVE-2026-86117 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-86117)
Finding 05 — Webstudio: Server-Side Request Forgery
What changed: Webstudio through 0.296.0 contains an unauthenticated server-side request forgery vulnerability in the /cgi/image, /cgi/video, and /cgi/asset proxy routes when RESIZE_ORIGIN environment variable is unset. Attackers can supply arbitrary URLs to these endpoints to read cloud instance metadata, access internal services, and perform network reconnaissance on the instance infrastructure.
Technical evidence: CVE-2026-86119; CVSS v4.0 9.2; weakness CWE-918; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Configure RESIZE_ORIGIN to restrict proxy routes to trusted origins, and restrict outbound access from the Webstudio host to metadata endpoints and internal network ranges. Monitor the three /cgi/ proxy routes for absolute URLs and loopback, link-local or private-IP destinations. ([ionix.io](https://www.ionix.io/threat-center/cve-2026-86119/), [github.com](https://github.com/webstudio-is/webstudio/issues/5816), [cve.org](https://www.cve.org/CVERecord?id=CVE-2026-86119))
Affected: Self-hosted Webstudio through 0.296.0 when RESIZE_ORIGIN is unset; the hosted webstudio.is SaaS is not affected. ([ionix.io](https://www.ionix.io/threat-center/cve-2026-86119/), [github.com](https://github.com/webstudio-is/webstudio/issues/5816))
Panel assessment: Patch affected self-hosted Webstudio deployments now because this is unauthenticated SSRF with a proof of concept and the blast radius can extend from the web app host into cloud metadata and internal network paths. The likely attack path is a crafted absolute URL sent to /cgi/image, /cgi/video, or /cgi/asset, causing the server to fetch metadata or private endpoints and exposing credentials, internal services, or data reachable from that instance. (priority: patch now)
Action: Map CVE-2026-86119 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-86119)
Finding 06 — SQL Chat: Server-Side Request Forgery
What changed: SQL Chat contains four unauthenticated API endpoints that accept client-supplied database connection parameters and execute arbitrary SQL queries against attacker-specified hosts. Attackers can connect to internal databases, execute SQL commands, enumerate schemas, and pivot into the server's network without authentication.
Technical evidence: CVE-2026-86123; CVSS v4.0 9.4; weakness CWE-918; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Place self-hosted SQL Chat behind authentication that gates every /api/connection/ route, and do not expose it directly to the internet. Restrict outbound access to internal/private address ranges, allow only approved database hosts, and monitor for unexpected destination hosts or ports. ([ionix.io](https://www.ionix.io/threat-center/cve-2026-86123/), [github.com](https://github.com/sqlchat/sqlchat/issues/189), [vulncheck.com](https://www.vulncheck.com/advisories/sql-chat-unauthenticated-database-connection-proxy-in-the-api-connection-endpoints))
Affected: sqlchat up to and including Git commit 665af875413affadfeefff81794f1d7758782bc2. ([vulncheck.com](https://www.vulncheck.com/advisories/sql-chat-unauthenticated-database-connection-proxy-in-the-api-connection-endpoints))
Panel assessment: Treat this as patch-now for any reachable SQL Chat deployment: unauthenticated endpoints, a public PoC, and server-side database connectivity make exposure more important than the low EPSS percentile, because compromise can jump from the web app into internal data paths. (priority: patch now)
Action: Map CVE-2026-86123 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-86123)
Finding 07 — OpenPanel: Server-Side Request Forgery
What changed: OpenPanel before 2.3.0 contains an unauthenticated server-side request forgery vulnerability in the /misc/favicon and /misc/og endpoints that accept an attacker-supplied url parameter with insufficient validation. Attackers can force the API to fetch arbitrary internal hosts and cloud metadata endpoints, with small responses returned verbatim enabling credential theft and internal service enumeration.
Technical evidence: CVE-2026-85612; CVSS v4.0 8.7; weakness CWE-918; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Require authentication on the /misc fetch/cache routes. Disable redirect following or revalidate every redirect hop. ([github.com](https://github.com/Openpanel-dev/openpanel/security/advisories/GHSA-2hff-m67f-2w2w), [vulncheck.com](https://www.vulncheck.com/advisories/openpanel-before-2.3.0-ssrf-via-favicon-and-og-endpoints))
Affected: OpenPanel versions from 0 up to, but excluding, 2.3.0. ([vulncheck.com](https://www.vulncheck.com/advisories/openpanel-before-2.3.0-ssrf-via-favicon-and-og-endpoints))
Fix: OpenPanel 2.3.0. ([github.com](https://github.com/Openpanel-dev/openpanel/security/advisories/GHSA-2hff-m67f-2w2w))
Action: Map CVE-2026-85612 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-85612)
Finding 08 — USN-8731-1: MiniUPnPd vulnerability
What changed: It was discovered that MiniUPnPd contained an integer underflow vulnerability in SOAPAction header parsing. A remote attacker could use this issue to cause a denial of service or information disclosure by sending a malformed SOAPAction header with a single quote.
Technical evidence: CVE-2026-5720; CVSS v4.0 7.1; weakness CWE-191, CWE-125; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Disable UPnP where it is not required; otherwise restrict access to UPnP services from untrusted network segments. Monitor for malformed or unusually short SOAPAction headers and unexpected MiniUPnPd crashes or restarts. Tenable reports that no known exploits are available. ([sentinelone.com](https://www.sentinelone.com/vulnerability-database/cve-2026-5720/), [tenable.com](https://www.tenable.com/plugins/nessus/307450), [vulncheck.com](https://www.vulncheck.com/advisories/miniupnpd-integer-underflow-soapaction-header-parsing), +1 more)
Affected: MiniUPnPd versions before 2.3.10. ([vulncheck.com](https://www.vulncheck.com/advisories/miniupnpd-integer-underflow-soapaction-header-parsing))
Fix: Ubuntu fixes are 2.3.9-2ubuntu0.1~esm1 for 26.04 LTS, 2.3.4-1ubuntu0.1~esm1 for 24.04 LTS, 2.2.3-1ubuntu0.1~esm1 for 22.04 LTS, 2.1-6.1ubuntu0.1~esm1 for 20.04 LTS, 2.0.20171212-2ubuntu0.1~esm1 for 18 ([ubuntu.com](https://ubuntu.com/security/CVE-2026-5720))
Action: Map CVE-2026-5720 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: ubuntu.com](https://ubuntu.com/security/notices/USN-8731-1)
Finding 09 — IBM Observability with Instana: Incorrect Authorization
What changed: IBM Observability with Instana (Agent) Build 1.0.303 through 1.0.323 IBM Instana Agent Operator could allow an authenticated remote attacker to obtain sensitive information, caused by missing destination namespace validation when copying etcd mTLS client credentials from the openshift-etcd system namespace into an attacker-controlled namespace. CVE coverage: CVE-2026-19283.
Technical evidence: CVE-2026-19283; CVSS v3.1 7.7; weakness CWE-863; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-19283 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-19283)
Finding 10 — Multiple vulnerabilities in IBM Langflow OSS 1.0.0
What changed: CVE coverage: CVE-2026-19298, CVE-2026-19303, CVE-2026-19304, CVE-2026-19305. The cited advisories disclose: through 1.11.2 could allow a remote authenticated attacker to execute arbitrary code due to an authorization bypass in the flow build process; through 1.11.2 could allow a remote authenticated attacker to delete arbitrary local files or directories due to improper limitation of a pathname to a restricted directory; through 1.11.2 could allow a remote authenticated attacker to obtain sensitive information from internal services due to a URL parser discrepancy; through 1.11.2 could allow a remote attacker to obtain sensitive information due to server-side request forgery.
Technical evidence: CVE-2026-19298; CVSS v3.1 8.8; weakness CWE-94; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-19298 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-19298)
Finding 11 — Multiple vulnerabilities in IBM i
What changed: CVE coverage: CVE-2026-18175, CVE-2026-18221. The cited advisories disclose: manipulate database transactions due to improper authorization in the DDM target dispatcher; gain unauthorized access due to improper validation of client-supplied authentication parameters.
Technical evidence: CVE-2026-18175; CVSS v3.1 8.1; weakness CWE-285; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Where DDM/DRDA is not required, block TCP ports 446, 447 and 448 at the IBM i server using CFGTCP port restrictions. VulDB reports no publicly available exploit for either CVE. ([ibm.com](https://www.ibm.com/support/pages/node/7286186), [ibm.com](https://www.ibm.com/docs/en/i/7.5.0?topic=network-ports-port-restrictions), [vuldb.com](https://vuldb.com/vuln/399012), +1 more)
Affected: IBM i 7.6, 7.5, 7.4 and 7.3. ([ibm.com](https://www.ibm.com/support/pages/node/7286186))
Fix: IBM i 7.6: PTFs SJ11231 and SJ11230; 7.5: SJ11232 and SJ11233; 7.4: SJ11262 and SJ11261; 7.3: SJ11234 and SJ11235. ([ibm.com](https://www.ibm.com/support/pages/node/7286186))
Panel assessment: Patch affected IBM i releases this week, prioritising any system where DDM/DRDA ports 446, 447 or 448 are reachable: there is no reported public exploit, but both issues are high severity and the blast radius is database access or transaction integrity rather than a narrow local defect. (priority: this week)
Action: Map CVE-2026-18175 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-18175)
Finding 12 — IBM ContextForge MCP Gateway <= v1.0.7 MCP Context Forge: Exposure of Sensitive Information to an Unauthorized Actor
What changed: IBM ContextForge MCP Gateway <= v1.0.7 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive credentials and escalate privileges due to improper validation of jq filters. CVE coverage: CVE-2026-18486.
Technical evidence: CVE-2026-18486; CVSS v3.1 8.8; weakness CWE-200; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-18486 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-18486)
Finding 13 — ILIAS before versions 9.22, 10.10.
What changed: ILIAS before versions 9.22, 10.10, and 11.3 contains a SQL injection vulnerability in the repository trash table where the table navigation sort field from HTTP requests is passed directly into the ORDER BY clause of a SQL query without validation against declared sortable columns. Authenticated users with write permission on any container can inject arbitrary SQL through the sort parameter, and because multi-statement execution is enabled in the database layer, stacked queries enable full database read and writ.
Technical evidence: CVE-2026-82538; CVSS v4.0 8.7; weakness CWE-89; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Restrict repository write permissions to trusted administrators and review ACLs regularly. Use web application firewall rules to block anomalous ORDER BY expressions in HTTP requests. ([app.opencve.io](https://app.opencve.io/cve/CVE-2026-82538), [vuldb.com](https://vuldb.com/vuln/399134), [vulncheck.com](https://www.vulncheck.com/advisories/ilias-arbitrary-sql-injection-via-repository-trash-table-sort-parameter))
Affected: ILIAS 9.0 to before 9.22, 10.0 to before 10.10, and 11.0 to before 11.3. ([vulncheck.com](https://www.vulncheck.com/advisories/ilias-arbitrary-sql-injection-via-repository-trash-table-sort-parameter))
Fix: ILIAS 9.22, 10.10, and 11.3. ([vuldb.com](https://vuldb.com/vuln/399134))
Action: Map CVE-2026-82538 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-82538)
Finding 14 — Multiple vulnerabilities in WordPress
What changed: CVE coverage: CVE-2026-19887, CVE-2026-15984, CVE-2026-16649, CVE-2026-77830, CVE-2026-19769. The cited advisories disclose: is vulnerable to PHP Object Injection in all versions up to, and including, 2.12.1 via deserialization of untrusted input in the Telecom EDY payment callback; is vulnerable to Stored Cross-Site Scripting via Custom Field Parameters in all versions up to, and including, 1.0.20 due to insufficient input sanitization and output escaping.
Technical evidence: CVE-2026-19887; CVSS v3.1 8.8; weakness CWE-502; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-19887 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-19887)
Finding 15 — Axolotl: Inclusion of Functionality from Untrusted Control Sphere
What changed: Axolotl through 0.18.0 contains a remote code execution vulnerability in the multipack patch path where trust_remote_code defaults to None instead of False, causing the security guard to be bypassed. Attackers can execute arbitrary Python code by crafting a malicious Hugging Face model repository selected as base_model, which is loaded with hardcoded trust_remote_code=True during AutoModelForCausalLM.from_pretrained.
Technical evidence: CVE-2026-86169; CVSS v4.0 8.7; weakness CWE-829; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Analyst note: Set trust_remote_code: false explicitly. If remote code is unavoidable, permit only models pinned to a specific commit revision. ([docs.axolotl.ai](https://docs.axolotl.ai/docs/config-reference.html), [huggingface.co](https://huggingface.co/docs/transformers/main/models), [github.com](https://github.com/axolotl-ai-cloud/axolotl/commit/b62d60b101eea7f32532ee3c0b17c2f2430a9262))
Action: Map CVE-2026-86169 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits:** fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-86169)