Authentication bypass in SiYuan's kernel CheckAuth function unconditionally grants administrator privileges (RoleAdministrator) to any HTTP request whose RemoteAddr is 127.0.0.1, affecting a specific set of endpoints including /api/system/exit, /assets/*, and /export/*, even when an access auth code is explicitly configured. All versions up to and including v3.7.2 are affected; v3.7.4 contains the vendor-released patch. The fixed-port reverse proxy forwards requests to the kernel over loopback without injecting authentication tokens or configuring trusted proxy headers, creating a theoretical remote unauthenticated attack path if the proxy is bound to a network-accessible interface - though per the advisory this remote scenario was established only by code inspection and was not reproduced end-to-end. No public exploit code exists and this CVE is not listed in the CISA KEV catalog.
IBM i Access Client Solutions versions 1.1.2.0 through 1.1.9.13 expose a publicly writable truststore, allowing a local authenticated attacker to inject a rogue certificate authority and subsequently intercept or manipulate TLS-protected communications. The writable truststore breaks the chain of trust at the client level, enabling man-in-the-middle attacks against sessions the client believes are cryptographically secured. No public exploit or active exploitation has been identified at time of analysis, and EPSS probability is extremely low at 0.09%.
Path traversal in SSH.NET's ScpClient.Download() enables a malicious, compromised, or man-in-the-middle SCP server to write arbitrary files anywhere the client process has write access during recursive directory downloads. All SSH.NET NuGet package versions up to and including 2025.1.0 are affected; the vulnerability is analogous to CVE-2019-6111 in OpenSSH but extends to directory traversal. No public exploit code or CISA KEV listing has been identified at time of analysis, though the integrity impact is high given the file-write primitive can overwrite SSH authorized keys, shell rc files, or application binaries.
Symlink-following jail escape in the ansible-jailexec FreeBSD connection plugin (versions through 1.3.0) allows a party controlling content inside a managed jail to achieve arbitrary root-owned file writes on the jail host. The put_file method resolves transfer destinations as the jail's filesystem root concatenated with the task's target path, then executes mkdir -p and mv on the host as root - outside the jail's chroot - enabling any symlink planted inside the jail to redirect those writes to arbitrary host paths. An attacker already present inside a managed jail who can anticipate or observe Ansible playbook execution can thereby escape the jail boundary entirely, writing cron jobs, rc.d scripts, or authorized_keys entries to the host and achieving full host compromise. No public exploit has been identified at time of analysis; vendor-released patch 2.0.0 is available.