Path Traversal
Monthly
Directory traversal in Bisheng 2.3.0, 2.4.0, and 2.4.0-beta1 allows unauthenticated remote attackers to read arbitrary files from the server filesystem through the Linsight task-execution endpoint implemented in src/backend/bisheng/linsight/domain/task_exec.py. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates no authentication or user interaction is required against default configurations, with impact bounded to confidentiality - disclosure only, no code execution or file modification. Publicly available exploit code exists (SSVC exploitation status 'poc'; a public gist accompanies the report), but the vulnerability is not confirmed actively exploited (no CISA KEV entry), and EPSS is low at 0.33% (24th percentile), so priority should be driven by whether an organization actually exposes a Bisheng instance to untrusted networks.
Directory traversal in Agent Zero 1.7 through 1.10 lets the AI agent's file-browser component read files anywhere on the host, because FileBrowser is initialized with the host root as its workspace rather than a confined sandbox. The CVSS 3.1 vector is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), which models unauthenticated network access, but the practical risk is gated by whether the Agent Zero UI is exposed to untrusted networks; Agent Zero is often a local single-operator tool, so the AV:N/PR:N rating only applies when that interface is deliberately reachable without an authentication layer. At time of analysis there is no confirmed active exploitation (no CISA KEV entry) and no public exploit identified at time of analysis, and EPSS is 0.33% (24th percentile), indicating low predicted exploitation activity; reference material consists of a GitHub issue and a gist.
Directory traversal in Bisheng 2.3.0, 2.4.0, and 2.4.0-beta1 lets a remote attacker use crafted filename/path input to break out of the intended download/cache directory through the save_download_file routine (src/backend/bisheng/core/cache/utils.py:290), yielding arbitrary file read and write with a CVSS 3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). The vector indicates an unauthenticated, network-reachable attack with no user interaction, though the practical limiting factor is whether the API route that reaches save_download_file is exposed without a login - defenders should verify that against their own deployment before assuming unauthenticated reachability. Exploitation status: no public exploit identified at time of analysis, and there is no CISA KEV entry; EPSS is 0.33% (24th percentile), so mass exploitation is not currently expected, but the impact per successful attack is severe given the high confidentiality and integrity ratings and the absence of any availability impact.
Directory traversal in agent-zero 1.7 through 1.10 allows remote attackers to write files to arbitrary locations outside the intended file-browser directory via the save_file_b64 method, with the evaluated CVSS vector indicating PR:N/UI:N and high integrity impact according to the authoritative assessment. No CISA KEV listing was provided, and no public exploit identified at time of analysis; EPSS is 0.33% (24th percentile), and the supplied CVSS 3.1 score is 7.5, though the independent assessment shifts the impact from confidentiality to integrity (C:N/I:H/A:N) because exploitation concerns unauthorized file writes rather than reads.
Path traversal in the WatchGuard Fireware OS WebUI management agent lets an authenticated administrator read or list arbitrary files on the local filesystem by submitting a specially crafted management request. Exploitation requires valid WebUI administrator credentials (the highest management privilege on the Firebox), per the assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, so the flaw is remote and low-complexity once the attacker already holds admin access, and the impact is limited to confidentiality (file read/list) with no write, code execution, or availability effect. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the vendor advisory is published at https://psirt.watchguard.com/CVE-2026-13224 and no EPSS score was provided in the available data.
Missing authorization in the wgagent management daemon of WatchGuard Fireware OS allows an authenticated, low-privileged management account - including read-only or guest administrator roles - to crash the daemon and read files accessible to its process by sending a crafted request to the management API. The weakness sits in the daemon's session-initialization function, which fails to enforce proper privilege validation before handling attacker-controlled input; the associated path-traversal class (CWE-22) is what enables the arbitrary file read, while the crash produces a denial-of-service condition against the agent. Exploitation requires a valid management session and network reachability to the management plane (CVSS 4.0: 7.1, PR:L, VA:H, VC:L), so risk concentrates on Fireboxes with exposed or broadly accessible management interfaces, multi-admin/multi-tenant deployments, and environments where guest or read-only admin accounts are provisioned. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Toptech Systems TMS7 and TopHat expose a file export endpoint that lets any network-reachable, unauthenticated attacker submit a single crafted POST request and pull arbitrary database tables out of the system - an information disclosure of the highest severity as scored by CISA ICS (CVSS 10.0), and assessed by our analysis as AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, i.e. confidentiality-only impact with no integrity or availability effect. Affected are deployments of Toptech TMS7 (all versions captured in CPE with a wildcard version) and TopHat, which are OT/ICS fuel-terminal and terminal-automation products typically expected to sit on segmented operational networks; the decisive factor for real-world exploitability is whether the export endpoint is reachable from outside that trusted OT segment, since no authentication, user interaction, or non-default toggle is required. There is no public exploit code identified at time of analysis and the flaw is not listed on CISA KEV, so exposure should be treated as a configuration-and-segmentation problem rather than a confirmed ongoing campaign. Authentication requirements are not in question here: the CVSS vector contains PR:N, so exploitation is unauthenticated.
Path traversal in VLC media player's skins2 ThemeLoader (before 3.0.24) allows attackers to write arbitrary files with VLC user privileges by crafting a malicious .vlt skin archive, enabling code execution through Lua script injection. Exploitation requires the victim to run the non-default skins2 interface and open the malicious skin, so local user interaction and social engineering are needed. No public exploit code has been identified at time of analysis, and the CVSS 4.0 score is 8.5 (assessed as CVSS 3.1 7.8 due to local attack vector and user interaction).
IBM DataStage on Cloud Pak for Data 5.4.0.0 contains a path traversal flaw in its archive extraction routine that lets a remote attacker with a valid authenticated account write files outside the intended destination directory and ultimately execute arbitrary code with the privileges of the affected service (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H). The root cause is CWE-22 improper limitation of a pathname to a restricted directory, commonly known as an archive 'zip-slip' condition, where crafted entries in an uploaded archive escape the extraction root. Authentication is mandatory, so this is not an unauthenticated flaw; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the realistic risk is concentrated in enterprise Cloud Pak for Data deployments where the attacker already holds platform credentials or a foothold.
Path traversal in IBM Guardium Data Protection 12.2's Datasource REST component allows authenticated remote attackers with low privileges to delete arbitrary files, causing denial of service and integrity impact. The flaw requires network access to the REST API and valid credentials (CVSS PR:L), with no user interaction. No public exploit code or active exploitation has been identified at time of analysis, but a vendor patch is available.
Unauthenticated content and configuration tampering in Marmite's optional built-in development server (all versions through 0.4.2) lets any network-reachable attacker create, modify, or overwrite site content and configuration by posting to the /__marmite__/content, /__marmite__/config, and /__marmite__/file/ endpoints, with no credentials or user interaction required. The same handlers pass unsanitized path parameters from handle_create_content and handle_clone_content into filesystem writes, so an attacker can traverse out of the project directory and drop or clobber files elsewhere on the host. Exploitation requires the target to be running `--serve` and reachable over the network - pre-0.4.3 the server bound to 0.0.0.0:8000 by default, and production static sites served by Nginx or Apache are unaffected; no public exploit code was identified at time of analysis, and the vendor released 0.4.3 to fix the issue (loopback-by-default binding plus a documented development-only posture).
Unauthenticated path traversal in Marmite's built-in development server (--serve) lets remote attackers read arbitrary files that the marmite process can access, by submitting percent-encoded '..' sequences that the handle_request function in src/server.rs fails to reject after decoding and path-joining. All versions through 0.4.2 are affected, and exposure is significant because the server previously defaulted to binding 0.0.0.0:8000 (all interfaces) rather than loopback, so any host running --serve on a network-facing address was reachable; the 0.4.3 fix commit narrows the default bind to 127.0.0.1 and labels the server development-only. No public exploit identified at time of analysis and the component is a development-only preview server, but the CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N/VC:H, 8.7) reflects a low-complexity, unauthenticated high-confidentiality read with no integrity or availability impact.
Unauthenticated path traversal in Balbooa Forms (a Joomla extension) before 2.4.3.4 allows remote attackers to exfiltrate local files readable by the Joomla process via crafted upload-field JSON during public form submission. The flaw requires that the target form has both the 'auto reply' and 'attach uploaded files' options enabled, limiting exploitability but still posing high risk given the CVSS 4.0 score of 8.9 and no authentication or user interaction required. No public exploit code has been identified at time of analysis, and no active exploitation has been confirmed via CISA KEV.
Arbitrary directory deletion in Joomla CMS affects versions 4.0.0 through 5.4.8 and 6.0.0 through 6.1.3, where a backend user holding administrator-level privileges (CVSS PR:H) can pass a cache group name containing path-traversal sequences that the file-based caching layer fails to sanitize, causing the cache purge action to remove directories outside the intended cache path. The result is high integrity and availability impact with no confidentiality loss, rated 7.0 under CVSS 4.0 (AV:N/AC:L/PR:H/UI:N/VC:N/VI:H/VA:H) and assessed at CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H by independent analysis. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the high-privilege prerequisite confines realistic risk to insider or compromised-administrator scenarios rather than opportunistic remote attackers.
Local privilege escalation in TeamViewer Full Client and Host on Windows, Linux, and macOS (all versions prior to 15.82) allows an authenticated low-privileged local user to write arbitrary files with SYSTEM/root privileges by sending crafted IPC commands to the locally running privileged TeamViewer service daemon. Successful exploitation yields full compromise of confidentiality, integrity, and availability on the host (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and because the flaw is deterministic rather than a race condition it is reliably triggerable once local access exists. No public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); however, the requirement of only low-privileged local access makes it a valuable post-compromise escalation primitive.
Path traversal in Wireshark's configuration-profile import handler (CWE-22) allows a maliciously crafted profile to write files outside the intended profile directory, crashing the application and potentially achieving code execution in the user's context. Affected releases are Wireshark 4.4.0 through 4.4.18 and 4.6.0 through 4.6.8; the flaw is rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R) and requires the victim to manually import the attacker-supplied profile, so exploitation depends on social engineering rather than a network-facing or automatic trigger. Publicly available exploit code exists and the issue is tracked as wnpa-sec-2026-106, but it is not confirmed as actively exploited (CISA KEV) and EPSS is low at 0.19% (7th percentile), making this a moderate-priority issue rather than an emergency; patched releases 4.4.19 and 4.6.9 are available from the vendor.
Unauthenticated network attackers can exploit a directory traversal flaw in the file-upload feature of Hitachi Energy RTU500 Series CMU firmware to write or overwrite arbitrary files on the device filesystem, potentially modifying device data or disrupting operation. The issue has a CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), reflecting high integrity and availability impact with no confidentiality impact. This is a genuine high-priority issue rather than a high-CVSS-but-low-risk artifact, but no public exploit code or confirmed active exploitation was identified at time of analysis, and practical exposure is limited by the typical OT network isolation of RTU500 substation devices.
Remote authenticated attackers can write files to arbitrary locations in Flowring Agentflow 4.0 via a path traversal flaw in the /WebAgenda/download/uploadFile.jsp endpoint, affecting versions released before March 24, 2023. The vulnerability requires a low-privilege authenticated session and no user interaction, with a CVSS 4.0 base score of 7.1. No public exploit code or active exploitation has been identified at the time of analysis.
Authenticated users holding backup or restore privileges on affected FreePBX deployments can achieve remote code execution through the backup Module on versions prior to 16.0.72 and 17.0.7. Improper path sanitization during backup restore lets a crafted archive place attacker-controlled PHP files directly into the web root, where the FreePBX web server will execute them, giving the attacker full control of the host and, by extension, the underlying Asterisk telephony platform (CVSS:4.0 8.6; independent assessment scores CVSS:3.1 8.8, AV:N/AC:L/PR:L/UI:N with high confidentiality and integrity impact). Exploitation is not pre-authentication: it requires a valid account with sufficient access permissions and/or write access to backup files plus network reachability of the FreePBX administration interface, and no public exploit code has been identified at time of analysis. This is a high-priority issue for internet-exposed or broadly permissioned FreePBX instances rather than a drop-everything emergency, since the primary attack surface is a privileged administrative workflow.
Authenticated remote code execution in FreePBX (versions prior to 16.0.10 and 17.0.5) lets an attacker who possesses a valid, known username abuse the sound-language upload and conversion workflow to write arbitrary files, including malicious PHP, into the web server's document root. The root cause is a path-traversal weakness (CWE-22) in the conversion step where path sanitization is insufficient, and successful exploitation gives full confidentiality, integrity and availability impact on the PBX host (vendor CVSS v4.0 8.7; independent assessment CVSS v3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, so authentication - not user interaction - is the gate). No CISA KEV entry and no public exploit code were identified at time of analysis, meaning this is a high-severity, patch-now issue for PBX administrators rather than a mass-exploitation emergency; practical risk concentrates where FreePBX administrative panels are internet-facing or protected by weak or default operator credentials, and is reduced where the panel is network-segmented.
Archive extraction in the Node.js decompress package allows a crafted archive containing chained symlink entries to resolve file writes outside the intended output directory, because the default decompress(input, output) API relies on lexical path containment checks that the kernel's symlink resolution can bypass. This affects @xhmikosr/decompress before 10.2.2 and before 11.1.4, and the separately maintained but unmaintained kevva/decompress package through 4.2.1, which remains unpatched. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:N, 9.1) indicates unauthenticated remote triggering with high confidentiality and integrity impact; writing outside output can overwrite startup scripts or configuration and escalate to remote code execution, and the flaw is a bypass of the incomplete hardening previously applied for CVE-2026-53486. Exploitation requires the consuming application to extract an attacker-influenced archive on a non-Windows platform (Windows emulates symlinks via hardlinks and does not follow the affected path), and no public exploit code was identified at time of analysis, though the upstream fix ships a regression test that documents the escape technique.
Authenticated path traversal in Apache Karaf before 4.4.12 allows a principal holding the shipped 'manager' role to write attacker-controlled content to arbitrary files writable by the Karaf process, because ConfigRepositoryImpl.update() and createFactoryConfiguration() build the target configuration filename from caller-supplied input without confining the result to ${karaf.etc}. Under Karaf's default command/JMX ACL (org.apache.karaf.command.acl.conf.cfg maps 'update = manager'), this lets a manager-role user overwrite files the same ACL reserves to 'admin' - such as etc/users.properties, etc/*.acl.*.cfg, and etc/org.apache.karaf.management.cfg - and thereby grant themselves the admin role or take over the container. The advisory does not indicate active exploitation, and no public exploit code has been identified at time of analysis; EPSS is 0.17% (6th percentile), indicating low predicted exploitation, while published scoring (CVSS 9.8, PR:N) is more severe than this assessment, which requires an authenticated manager-role principal (PR:L) on a deployment that exposes Karaf management and grants manager to non-admins.
Path traversal in Flatpak's app deployment handling of the exported files/etc directory allows a malicious Flatpak application to empty or replace host files such as /etc/passwd, /etc/group, /etc/machine-id, or /etc/resolv.conf with a symlink when that app is installed or upgraded; on system-wide installations the write is carried out as root. Exploitation is gated on user interaction: the victim must choose to install or upgrade the attacker-supplied app from an untrusted source (CVSS 3.1 base 7.1, AV:N/AC:L/PR:N/UI:R with high availability and low integrity impact), making this a genuine but moderate-priority integrity/availability issue rather than a critical remote code execution flaw. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Path traversal in Flatpak's handling of the export/bin directory during application deployment allows a malicious Flatpak app to delete attacker-chosen files outside the deployment directory when that app is installed or upgraded; on system-wide installations the deletions are carried out with root privileges, so a crafted package can remove arbitrary files anywhere the deployer can reach. The flaw affects Flatpak releases before 1.18.4 and is triggered by a user or administrator installing or upgrading an attacker-supplied app, which supplies the required user interaction rather than a network-based trigger; the CVSS vector carries PR:N, so no prior authentication is needed beyond that install action. No public exploit code has been identified at time of analysis and there is no evidence of confirmed active exploitation, though the integrity and availability impact is high (arbitrary file deletion) and the flaw crosses a privilege boundary on system-wide installs.
Authenticated path traversal in Logsign SIEM versions 6.4.101 through 6.4.116 allows a low-privileged user to write arbitrary files to the underlying filesystem. The vulnerability (CWE-22) is reachable over the network via the web/API interface with no user interaction, and the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L) indicates high integrity impact and low availability impact but no confidentiality impact, consistent with an arbitrary file write primitive rather than file read. No public exploit code has been identified at time of analysis, and the issue is fixed in version 6.4.117; the vendor advisory is available via Turkish CERT (TR-26-1202). EPSS score was not provided.
Path traversal in the btrfs storage driver of Canonical LXD 4.0.2 and later allows an authenticated client that holds project-scoped permission to create instances to delete arbitrary files on the host as root by supplying a crafted subvolume path containing ../ sequences, and on hosts whose root filesystem is itself btrfs the same primitive escalates to placing attacker-controlled content at arbitrary host paths for full host compromise. The issue is rated CVSS v3.1 9.6 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H), reflecting a scope-changing breakout from a restricted tenant role into the host root context rather than a CVSS-inflated score, since a legitimate but limited project credential is the only prerequisite. No CISA KEV listing and no public exploit code were identified at time of analysis; vendor fixes are available in LXD 4.0.14, 5.0.10, 5.21.8 and 6.10.
Path traversal in Canonical LXD's Btrfs storage driver allows an authenticated user with instance-creation privileges to escape the intended backup import target and delete or replace arbitrary files and directories on the host as root, by supplying a crafted subvolumes[].path value in backup/optimized_header.yaml during a btrfs 'optimized' backup import. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, 9.9) reflects high confidentiality, integrity and availability impact with a scope change because the traversed write lands outside the LXD daemon's own container boundary; exploitation requires valid low-privilege API credentials and a Btrfs-backed host, not anonymous access. No public exploit code has been identified at time of analysis, and the issue is not confirmed actively exploited (CISA KEV), but the low attack complexity and root-level file-system effect make it a genuine high-priority fix rather than a CVSS-inflated score.
Remote, unauthenticated attackers can retrieve arbitrary local files from Dayforce Payroll by calling its file-download functionality with an absolute path or directory-traversal sequence in the file path parameter, with the server returning the file contents directly in the response. The issue is scored CVSS 4.0 9.2 (vendor/NVD) - network-reachable, low complexity, no privileges or user interaction required, high confidentiality impact, and a scope change to subsequent systems - making payroll data, PII, credentials and configuration secrets the realistic target set. Because vendor contact attempts were unsuccessful, only version R2026.2.0 is confirmed affected and the full version range remains unknown; no public exploit code has been identified at time of analysis.
Path traversal in the Rust-based pacquet package-manager component shipped inside pnpm allows a crafted lockfile to create symlinks and directories outside the project or node_modules boundary during installation. Only pnpm npm-package versions 12.0.0-alpha.0 through 12.0.0-alpha.4 that bundle pacquet are affected, and exploitation requires the victim to explicitly run an install with --trust-lockfile or a frozen lockfile against an attacker-supplied lockfile, so the trust flag that bypasses re-resolution is the enabling condition rather than a remotely reachable flaw. Impact is integrity-focused (CVSS 7.1, CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L), and no public exploit code was identified at time of analysis.
Authenticated directory deletion in the Event Gallery extension for Joomla (svenbluege.de) below version 6.5.0 allows a high-privileged Joomla backend user to supply a traversal payload in the `images` parameter of the `cache.process` clear-cache task and recursively delete any directory the web server account is permitted to write to. The impact is confined to integrity and availability of web-server-writable paths - there is no confidentiality loss (VC:N/SC:N) and no privilege gain beyond the actor's existing administrator-level access, which is the main limiting factor (PR:H), giving a CVSS 4.0 base score of 7.0. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the root cause is a CWE-22 path traversal that accepts unsanitised relative paths before file deletion.
Unauthenticated path traversal in the lomart.fr UP extension for Joomla (versions 5.0.0 through 5.2.0 and 6.0.0 through 6.0.29) allows remote attackers to read files outside the intended plugin directory, exposing configuration files, credentials and other sensitive data under the web root's readable filesystem. The reported CVSS 4.0 score is 9.2, and the independently assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms a confidentiality-only impact with no authentication or user interaction required, while integrity and availability remain unaffected. Real-world risk is governed by deployment scope rather than exploitability: this is a niche third-party Joomla extension, no public exploit was identified at time of analysis, and only sites that have the plugin installed and enabled at an affected version are exposed.
Unauthenticated remote code installation in the lomart.fr 'UP' plugin for Joomla (versions 5.0.0-5.2.0 and 6.0.0-6.0.29) allows remote attackers to write and install arbitrary code on affected sites without authentication, user interaction, or non-default configuration, as reflected in the vendor's CVSS 4.0 base score of 10.0. The flaw is a path traversal (CWE-22) that lets attacker-supplied paths escape the intended directory and place executable content where the web server will run it, giving full compromise of confidentiality, integrity, and availability on the host and follow-on systems. This is a niche, single-vendor Joomla add-on, so exposure depends entirely on whether the plugin is installed and active; no public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing).
Cross-namespace information disclosure in Kyverno before 1.19.1 allows an authenticated low-privilege tenant to read resources from other namespaces by abusing the apiCall context entry in namespaced Policy resources. The attacker crafts percent-encoded dot-segments in urlPath so that Kyverno's validation and execution stages interpret the path inconsistently, ultimately using the admission controller's ServiceAccount credentials to fetch data across the namespace boundary. Exploitation requires the ability to create or modify namespaced Policy resources and a multi-tenant deployment where namespace isolation is the security boundary; no public exploit identified at time of analysis, and a vendor patch is available in Kyverno 1.19.1.
Privilege escalation in Kyverno before 1.19.1 allows an authenticated Kubernetes namespace tenant with Policy/apiCall authoring rights to escape namespace isolation and create objects as Kyverno's admission-controller ServiceAccount. The attacker supplies percent-encoded directory-traversal sequences in the Policy apiCall urlPath to bypass the per-namespace clamp, enabling creation of cluster-wide MutatingWebhookConfiguration objects or PolicyException objects in the kyverno namespace, with a path to cluster-admin escalation. No public exploit identified at time of analysis; vendor patch available in 1.19.1.
Symlink-following flaws in Hugo's theme and module mount confinement allow files outside a project's mount roots to be read during a site build and, via static mounts, published into the public/ output directory. The flaw affects Hugo builds after v0.123.0 and before v0.166.0 for any project that adopts an untrusted theme checked into themes/ or a vendored (non-Go-modules) module containing a symlink at a mount root and then runs a build; the vendor scores this 8.7 (High) under CVSS 4.0, while independent analysis models it as CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N because the site operator must first adopt the malicious theme and execute the build. No public exploit code identified at time of analysis and no KEV listing; a vendor-released patch exists in v0.166.0.
GitPython before 3.1.62 is vulnerable to a path traversal (CWE-22) in Submodule.update() that allows unauthenticated remote attackers to create, populate from a submodule URL, and potentially delete directories outside the repository working tree when an application updates submodules at a non-HEAD (historical) commit. The flaw stems from the `path` field in an untrusted .gitmodules file being used without the _to_relative_path() containment guard that is applied in add() and move(). Exploitation requires an application flow that checks out submodules at a historical commit and an attacker-controlled repository; the standard clone-then-update flow re-derives the path from a canonical tree lookup and is not affected. No public exploit code or confirmed active exploitation (CISA KEV) exists at time of analysis, and the independent assessment rates real-world priority as low-to-medium despite the vendor's CVSS 4.0 score of 8.7.
Remote code execution via arbitrary file write affects Budibase Server versions before 3.45.0. An authenticated attacker holding the BUILDER role can upload a crafted ZIP to the PWA icon upload endpoint that exploits missing symlink validation during extraction, using leaf symlink entries followed by duplicate file entries to overwrite arbitrary files as root. This allows root-level code execution; no public exploit code has been identified at time of analysis, and the vulnerability is not reported as actively exploited.
Authenticated path traversal in SiYuan before v3.8.4 enables an administrator to write arbitrary files and create directory trees outside the workspace boundary via the setNotebookIcon endpoint. By injecting ../ sequences in the notebook parameter, the kernel process can write conf.json and other files to any location the process account can access. Exploitation requires a valid administrator session, so the realistic threat is a malicious or compromised admin rather than an anonymous remote attacker; no public exploit code has been identified, and CISA KEV does not list this issue.
Path traversal in the checkoutRepo endpoint of SiYuan (siyuan-note:siyuan) before v3.8.4 lets an authenticated administrator supply a sessionID parameter containing ../ sequences and overwrite JSON files in pre-existing directories that the SiYuan kernel can already write to, including locations outside the workspace. Integrity impact is high (CVSS 4.0 base 8.3; assessed CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L) but there is no confidentiality impact, no ability to create new files or write non-JSON content, and the PR:H requirement confines realistic abuse to a rogue or compromised administrator rather than an opportunistic remote attacker. No public exploit identified at time of analysis, and the issue is assessed as a moderate, not top-tier, priority.
Path traversal in SiYuan's exportBrowserHTML endpoint lets an authenticated administrator write attacker-controlled HTML into an index.html file outside the workspace directory, affecting all releases before v3.8.4. By supplying a folder parameter containing traversal sequences (such as ../../), an attacker with administrator privileges can overwrite any pre-existing, kernel-writable index.html location, achieving stored cross-site scripting or defacing the workspace. The issue is rated 8.3 (CVSS 4.0) with high integrity impact and low availability impact, requires high privileges (PR:H) and no user interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis; upgrading to v3.8.4 resolves it.
Sensitive local file disclosure in OpenClaw before 2026.8.1 lets a low-privileged caller (PR:L per the CVSS vector, not fully anonymous) smuggle an unvalidated absolute host path past sandbox path validation by supplying structured message attachments that carry multiple 'source' fields, hiding the disallowed path behind an allowed attachment source. When the Telegram delivery channel is configured and active, the agent then reads the referenced host file and relays it out through that channel, giving the attacker high-confidentiality read access to files that policy would otherwise reject. There is no code execution, file modification, or denial of service; EPSS and KEV data are not provided, and no public exploit code has been identified at time of analysis. The vendor has released a fix, and exploitation requires both a message-submission-capable attacker and an OpenClaw deployment that uses Telegram delivery.
Authenticated path traversal in Laranode before 1.2.1 lets any tenant holding a valid account and file manager access write arbitrary files outside their own home directory via the POST /filemanager/upload-file endpoint, including dropping PHP files into other tenants' web roots for code execution as those tenants. The endpoint built its destination as '/home/' + systemUsername + '/' + user-supplied path with no normalization or containment, so a low-complexity traversal request is sufficient on multi-tenant hosts where the web server interprets the written PHP; vendor CVSS 4.0 rates this 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) equally reflects cross-tenant scope change. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV entry); exploitation requires authentication, so single-tenant installations limit the blast radius to the attacker's own account.
Authenticated administrators of ClipBucket v5 who hold the manage_template_access permission can abuse a path traversal in the admin template editor (template_editor.php) to write attacker-controlled PHP files outside the intended styles/layout directory and have them executed as the web server user, yielding remote code execution on all versions before 5.5.3-#197. Publicly available exploit code exists (a HackMD writeup linked from the CVE record), and the vendor has released a fix in commit f31de49b and release tag 5.5.3-#197; the bug is access-gated by the administrator privilege and permission requirement (CVSS 4.0 base 8.6, PR:H), and there is no confirmed active exploitation in CISA KEV. This is a genuine but access-gated risk that primarily matters where multiple admin accounts exist or admin credentials are weak or reused.
GLPI 11.0.0 through 11.0.7 allows an authenticated attacker holding the form-administration privilege to achieve remote code execution by importing a crafted form with an illustration or scene identifier containing path-traversal sequences, causing a file to be written outside the intended custom-asset directory and into a servable or executable location. The CVSS 4.0 base score is 9.4 (Critical), and exploitation requires an authenticated admin session (PR:H) with no user interaction. No public exploit code has been identified at time of analysis; the vendor has released version 11.0.8 to fix the issue.
Insufficient path validation in GLPI's profile-picture update flow lets any authenticated user - including ordinary self-service accounts with no administrative rights - force the application to delete an attacker-selected file on the server's filesystem. Affected releases are GLPI 10.0.0 through 10.0.25 and 11.0.x before 11.0.8; the flaw is fixed in 10.0.26 and 11.0.8. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the CVSS 4.0 base score of 8.5 reflects a remote (AV:N), low-complexity (AC:L) attack with high integrity and availability impact once a valid low-privilege session (PR:L) is obtained.
Authenticated path traversal in the websocket/long-polling session handling of Zammad 7.0.2 and 7.1.0 allows a low-privilege logged-in user to delete arbitrary files and directories on the server with a single crafted request. The client-supplied session (client) identifier is insufficiently validated before being interpolated into internal filesystem paths, so traversal sequences escape the session storage directory - but only on instances using the default file-based session store, since Redis-backed deployments are not affected. Confirmed impact is integrity and availability loss (arbitrary deletion, no read/exfiltration per the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H); there is no confirmed active exploitation (CISA SSVC exploitation: none) and no public exploit identified at time of analysis, though the flaw is fully automatable. Note that the published CVSS 4.0 score of 8.8 carries PR:N, which overstates ease of access - the independent assessment confirms authentication is mandatory.
Local file inclusion in InvoicePlane before 1.7.2 allows an authenticated low-privileged user who can influence the e-invoice xml_id configuration to use path traversal sequences to include an existing .php file from the XMLconfigs helper directory. This is a moderate-priority, not urgent, finding: the advisory establishes local file inclusion, while full code execution would require a separate file-upload or file-write primitive, and no public exploit identified at time of analysis. The issue is fixed in version 1.7.2 via an allowlist on xml_id.
Authenticated path traversal in the Universal Connector Oracle Wallet upload component of IBM Guardium Data Protection 12.2 lets a low-privilege remote user write files to arbitrary filesystem locations on the appliance. The attacker must already hold a valid account with access to the Universal Connector upload function (PR:L) and must craft a traversal sequence that lands a file somewhere useful, which is why the vector carries AC:H despite the high confidentiality and integrity impact. Exploitation has not been observed: CISA SSVC records Exploitation as none and there is no public exploit identified at time of analysis, so this is a genuine but moderate-priority issue rather than a widespread emergency - though the 'total' technical impact rating means a successful hit against a misconfigured deployment could be severe.
Unauthenticated remote attackers who can reach an existing publicly shared Briefcase document can abuse unsigned save fields in Zimbra Collaboration Suite's OnlyOffice/Document Editing integration to perform path-traversal writes and execute commands as the zimbra service account. Exploitation is contingent on the non-default OnlyOffice/Document Editing add-on being enabled and on a supported Briefcase document being publicly accessible, so the 9.8 score in the source feed (AV:N/AC:L) is moderated by an independent assessment that rates attack complexity as High (AC:H) given those prerequisites. No public exploit code or confirmed active exploitation was identified at time of analysis, and no patched version could be confirmed from the single Zimbra wiki advisory reference provided.
Path traversal in IBM Guardium Data Protection 12.2 allows a remote attacker holding valid low-privilege credentials (CVSS PR:L) to escape a restricted directory and read sensitive files, delete arbitrary files, or execute arbitrary code on the appliance. The condition is not unauthenticated - it requires network reachability to the Guardium instance plus a legitimate low-privilege account - and attack complexity is rated high (AC:H), so exploitation depends on crafting path inputs that satisfy conditions outside the attacker's full control. No public exploit code has been identified and the flaw is not confirmed actively exploited (no CISA KEV listing), though vendor patch guidance is available and the CVSS score of 7.5 reflects the high confidentiality, integrity and availability impact if the traversal succeeds.
A use-after-free race condition in QEMU's 9pfs (virtfs) passthrough subsystem allows a malicious guest user to escape the shared directory boundary and read or write arbitrary files on the host, potentially achieving code execution as the QEMU process user (VM escape). Only hosts that have enabled 9pfs/virtfs host-directory sharing are exposed, since this is not a default configuration; the attacker must be a local guest user able to issue 9p protocol requests and must win a race between QEMU's main thread and a 9pfs worker thread with concurrent Tlcreate and Twalk requests. No public exploit code or active exploitation telemetry was identified at time of analysis, but the flaw is rated high severity (CVSS 8.8, scope-changed, C:H/I:H/A:H) and affects QEMU packages shipped in Red Hat Enterprise Linux 6 through 10, Red Hat OpenShift Container Platform 4, and related Red Hat products.
PHP code execution on Netgate pfSense Plus and pfSense CE firewalls can be achieved by an authenticated, highly privileged webGUI user who can modify Dashboard widget settings and plant a crafted .widget.php file on the filesystem, then set a widget sequence value containing path traversal so Dashboard index.php include()s and executes that file. The vendor rates this High (CVSS 8.5), while the independent assessment keeps AV:N/AC:H but raises the privilege requirement to PR:H, reflecting that the attacker already needs substantial Dashboard and file-write access; it is not remotely exploitable without authentication. No public exploit or KEV-listed active exploitation was identified in the provided data, and Netgate has released fixed versions.
Path traversal in the HTTP server built into the Botslab G980H dash camera lets anyone already connected to the camera's own WiFi network retrieve files from its removable storage without authentication or user interaction. Readable content includes recordings, images, diagnostic logs and firmware files, which are exactly the artifacts a web server should never expose. CISA's ICS advisory ICSA-26-267-01 tracks the issue as CWE-22 and scores it 7.1 (High), driven entirely by confidentiality impact; proximity is the limiting factor, since the flaw is reachable only from the adjacent network and cannot be triggered from the general internet. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Arbitrary local file and directory deletion on Docmost deployments that use local storage, exploitable by any authenticated low-privileged user. An attacker stores a crafted avatarUrl value that is not confined to the intended avatar directory; when Docmost's avatar cleanup routine later consumes that stored value, it deletes files or directories reachable by the Docmost service account. The issue affects Docmost versions prior to 0.80.1 and is rated CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L) - high integrity impact, low availability impact, no confidentiality loss. There is no public exploit code identified at time of analysis, and exploitation requires a valid account, so risk is concentrated in multi-tenant or shared instances running local storage.
An authenticated Discourse user who can post content can bypass the administrator's `allowed_iframes` subpath restriction and embed iframe content from a path the administrator never authorized, affecting all Discourse releases prior to 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0. The allowlist guard did not treat literal backslashes as path separators after decoding percent-encoded dot segments, so a crafted iframe source passed the subpath check while browser URL normalization resolved the frame outside the permitted path; exploitation requires a victim to view the post and depends on the viewer browser's backslash normalization behavior, consistent with the assessed vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (limited confidentiality and integrity impact, no availability impact, scope change). This is a moderate, non-priority finding - no public exploit identified at time of analysis.
Path traversal in the pulpcore content upload API allows an authenticated user holding only low-privilege file-repository permissions to read arbitrary files accessible to the Pulp server process by submitting a crafted 'file:' URL through the 'file_url' parameter, which is dispatched to the file downloader despite an intended scheme check. Baseline impact is confidentiality loss on the Pulp host; in deployments that include Pulp Container the same flaw escalates to theft of the container registry token signing private key, enabling forged bearer tokens and unauthorized access to every private container repository in the registry. Downstream products embedding pulpcore are affected, including Red Hat Satellite 6, Red Hat Ansible Automation Platform 2, and Red Hat Update Infrastructure 4/5. There is no public exploit identified at time of analysis, and EPSS data was not provided; Red Hat tracks the issue under advisory https://access.redhat.com/security/cve/CVE-2026-90959.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote user holding valid low-privileged credentials to reach files outside the directory the application intends to restrict, producing a high integrity impact (I:H) and a limited availability impact (A:L) while the published vector shows no direct confidentiality loss. Exploitation is remote (AV:N) but rated high complexity (AC:H), meaning success depends on target-specific conditions such as exact file paths or platform state, and it requires a valid account (PR:L) with no user interaction (UI:N). No public exploit code or CISA KEV entry was identified at time of analysis, so this is a real but moderate-priority flaw for unpatched 5.4.0.0 deployments; IBM has published a fix through its support advisory.
IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker with low privileges to execute arbitrary operating system commands by exploiting a path traversal flaw (CWE-22). The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) yields a High severity score of 8.8, reflecting full compromise of confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis, and a vendor patch is available.
Path traversal in Delta Electronics DIAEnergie before 1.11.00.022 allows unauthenticated remote attackers to manipulate file paths on the host, with the CVSS vector indicating high integrity and availability impact but no confidentiality impact, which is consistent with arbitrary file writing, overwriting, or deletion rather than file disclosure. Exploitation is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) and requires only network reachability to the DIAEnergie web application - no credentials, user interaction, or non-default configuration are prerequisites. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so current risk is driven by intrinsic severity and exposure rather than observed exploitation in the wild. The practical threat hinges on exposure: DIAEnergie is a niche industrial energy-management platform typically deployed on segmented OT/enterprise networks, so internet-facing or broadly reachable management interfaces carry the highest risk.
Unauthenticated path traversal in the eesy_ID2WP - Publish InDesign HTML5 WordPress plugin lets any remote attacker read arbitrary files from the host server on any site running version 1.0.3 or earlier. The flaw is reached through the id2wp_path parameter and requires no authentication, no privileges, and no user interaction (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, 7.5 HIGH), with impact limited to confidentiality because the attacker can only retrieve files the web server process itself is permitted to read. No public exploit code has been identified at time of analysis and there is no confirmed actively exploited (CISA KEV) status; the practical risk is opportunistic scanning of WordPress sites that have this niche plugin installed and active.
Authenticated PaperCut NG and PaperCut MF administrators can achieve arbitrary command execution on the underlying host through the Scan-to-Fax component by supplying crafted fax provider settings that contain path-traversal sequences. Exploitation requires a high-privilege admin account (CVSS PR:H) and network reachability to the admin console, and publicly available exploit code exists per the CVSS 4.0 E:P metric; there is no confirmed active exploitation (CISA KEV). The practical risk is concentrated on internet-exposed or compromised admin interfaces rather than opportunistic mass exploitation, making this a serious post-authentication issue rather than a drop-everything emergency.
Authenticated local file inclusion and code execution affects the MasterStudy LMS WordPress plugin in versions from 3.5.29 up to (but not including) 3.7.50, where one display-style setting is used to build a template path without validation. Exploitation requires an authenticated WordPress account with the Contributor role or higher, and turns into arbitrary PHP execution only when a suitable PHP file already exists on the server. Publicly available exploit code exists (WPScan), but there is no confirmed active exploitation (not in CISA KEV) and SSVC rates exploitation as none and non-automatable, making this a high-priority, manually driven issue rather than an emergency; this is especially true for sites that do not permit untrusted users to register at Contributor level or above.
Unauthenticated path traversal in the OpenShift console's /locales/resource.json endpoint allows remote attackers to read arbitrary *.json files from the console pod filesystem by manipulating the lng and ns query parameters, exposing plugin manifests and configuration files, and potentially enabling traversal against registered dynamic-plugin backends. The flaw is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5) and affects Red Hat OpenShift Container Platform 4; no public exploit code has been identified at time of analysis and there is no CISA KEV telemetry, but per the independent assessment this remains a credible remote-attack priority because the endpoint is reachable without credentials and yields high-confidentiality reads. Impact is limited to information disclosure - integrity and availability are not affected per the assessed vector.
Path traversal in Plex Media Server before 1.43.3.10861 lets an attacker who can reach the /system/agents/media/get endpoint read files accessible to the targeted Plex user by supplying ../ sequences in the url parameter. The primary exploitation path requires a valid Plex session token (the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, i.e. authenticated), while a secondary, lower-barrier path lets a LAN-adjacent attacker supply a crafted X-Forwarded-For header that the server trusts as evidence of local context. Read access is nominally bounded by the victim account's permissions, but because the reachable files include the PlexOnlineToken store, successful exploitation escalates from file disclosure to full Plex account and server takeover; no CISA KEV entry or public exploit code appears in the supplied intelligence, and a vendor fix is available in version 1.43.3.10861.
Path traversal in Flatpak's `flatpak build-init` command allows an attacker-controlled SDK container to write arbitrary files outside the developer's working directory when that developer builds against the SDK using both the `--writable-sdk` and `--sdk-extension` flags. The root cause (CWE-22) is that the SDK's declared extension-point `directory` value is resolved through a path helper that does not reject `..` components, so a malicious SDK can steer writes outside the intended build root. The independently assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) is a local, user-interaction-dependent action rather than the remote 9.8 originally submitted; no public exploit code or confirmed active exploitation has been identified at time of analysis, and the attacker must convince the developer to consume a hostile SDK, which severely limits real-world exposure.
Arbitrary host filesystem writes are possible in Flatpak through the extra-data fetch path, and on system-wide installs those writes are performed as root, allowing a malicious or compromised remote to plant attacker-controlled files outside the application sandbox. Exploitation is unauthenticated on the attacker's side (PR:N) but requires user interaction (UI:R): the victim must install or update an application whose manifest uses the xa.extra-data-sources mechanism from a malicious or attacker-controlled repository, and full root-level impact additionally depends on a system install rather than a per-user install. Two defects combine - the files/extra directory is resolved through symlink-following path operations, and blob names taken from xa.extra-data-sources are not sanitized against '..' traversal. There is no public exploit identified at time of analysis and no CISA KEV entry; tracking is available through the upstream advisory GHSA-fqx6-vh4p-42cg and Red Hat's CVE/Bugzilla records.
Unauthenticated path traversal in ManageEngine OpManager and ManageEngine Network Configuration Manager versions before 12.8.671 allows remote attackers to read arbitrary files from the appliance. Because the CVSS vector is PR:N/UI:N (7.5, AV:N/AC:L), no credentials or user interaction are required against a default-reachable deployment - an attacker with network access to the web console can directly request files outside the intended document root and expose configuration, credential, or key material. Impact is confidentiality-only (C:H with I:N/A:N), so the flaw does not permit modification of data or cause denial of service. No public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); the main limiting factor is exposure, since these are typically internal management consoles rather than internet-facing services.
Every desktop application generated by Pake inherits two upstream template defaults that together hand native IPC functionality to untrusted web content, allowing scripts served from any HTTPS origin to invoke the application's own native commands, including download_file. The root cause is a wildcard Tauri capability ("remote": { "urls": ["https://*.*"] } in src-tauri/capabilities/default.json) paired with "withGlobalTauri": true in src-tauri/tauri.conf.json, which places window.__TAURI__.core.invoke() within reach of ordinary page JavaScript; because Tauri's access control list only validates plugin: commands and not commands registered by the application itself via generate_handler!, no permission entry is required to call them. Exploitation is unauthenticated per the assessed vector (PR:N) but requires user interaction (UI:R) - the victim must run the generated app and attacker-controlled JavaScript must execute inside it, whether directly or through third-party analytics, advertising, or a compromised CDN loaded by the wrapped site. Chained with the path traversal tracked separately as CVE-2026-82635, this escalates to arbitrary file write and persistent code execution; no public exploit identified at time of analysis, and the issue is fixed in Pake V3.17.0.
Path traversal in the attachment-handling logic of Foxit PDF Editor and Foxit PDF Reader lets a crafted PDF write an embedded attachment to a directory outside the intended secure area when the document is opened by a local user. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-73) and requires the victim to open the malicious file, so it is user-interaction-gated rather than remotely triggerable, and no authentication is required of the attacker (PR:N). The practical consequence is arbitrary file write under the privileges of the Foxit process, which can escalate into code execution only if the attacker manages to land a file in an execution-relevant location such as a startup or autorun path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS data was not provided.
Insufficient validation of embedded-resource file paths in Foxit PDF Editor and Foxit PDF Reader (CVE-2026-91801) lets an attacker embed traversal sequences in a PDF so that files are written outside their intended location when the document is opened or previewed, with a conditional path from that arbitrary-file-write primitive to code execution. Rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), the issue is a client-side parsing flaw: no authentication is required, but user interaction is mandatory and there is no network-facing or default-service exposure, so risk is bounded to users who process untrusted PDFs. No public exploit identified at time of analysis, and escalation to code execution remains conditional on a viable write target.
Path traversal in ABB Mint Workbench I through version 5876 allows any local user to reach files outside the intended restricted directory, giving high confidentiality impact on the vulnerable host and on a subsequent system while leaving integrity and availability untouched. Exploitation is gated by local access - the CVSS vector specifies AV:L with PR:N and UI:N - so exposure is confined to engineering workstations and commissioning laptops running the affected build rather than servers or internet-facing systems. No public exploit code and no confirmed active exploitation have been identified at time of analysis; ABB has published vendor advisory 9AKK108473A3188.
IBM Financial Transaction Manager (FTM) for Red Hat OpenShift fails to properly validate symbolic links, allowing an authenticated remote user to read files outside the intended path and disclose sensitive information held by the financial platform. The affected code path is reachable across the network (AV:N) but requires a valid FTM session (PR:L), and no public exploit code or confirmed active exploitation has been identified at time of analysis. IBM has published a vendor patch via its support portal; while the vendor-assigned CVSS of 9.9 implies a scope-changing, high-integrity and high-availability impact, independent analysis of the described weakness assesses it as an information-disclosure issue (file read) rather than full system compromise.
Path traversal in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift, affecting builds from 4.0.6.0 through 4.0.10.0 Interim Fix 06 (Operator 4.4.6+20260807.081800), allows an unauthenticated remote attacker (PR:N/UI:N per the CVSS vector) to submit manipulated path input that the product fails to canonicalize and thereby read arbitrary files accessible to the FTM process. The impact is confidentiality-only - no write, code execution, or availability effect - and exploitation requires network reachability to the FTM application endpoint, so internal-only routes or network segmentation materially reduce exposure. A vendor patch is available via IBM's advisory; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low at 0.35% (28th percentile), making this a moderate rather than urgent priority.
Arbitrary server-side code execution in the Plone process is possible through the Classic portlet shipped in plone.app.portlets 5.0.0 through 7.0.1, where user-supplied template and macro fields are assembled into a TALES path expression and then evaluated by the TAL path() helper, allowing a crafted value to be interpreted as a full expression rather than a constrained path. Any authenticated user who can add or edit a Classic portlet can execute code, and under Plone's default role map that includes ordinary registered users on their personal dashboard, so the issue amounts to a post-authentication privilege escalation across the trust boundary between a web user and the server-side Plone process (CVSS 3.1 9.9, scope changed: AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). There is no confirmed active exploitation (no CISA KEV listing) and no public exploit identified at time of analysis, but vendor patches are available in 5.0.8, 6.0.4, and 7.0.2.
Unauthenticated path traversal in Adobe Connect (and its Android mobile app component) lets a remote attacker read files outside the intended access scope on a network-reachable deployment. Per Adobe's CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N, 8.6), the attack needs no credentials and no user interaction, so an internet-exposed default installation is directly targetable; our independent assessment keeps the same network/low-complexity/no-auth/no-interaction profile but treats scope as Unchanged and stresses that impact is limited to reading files accessible to the Connect service account, with no write, no code execution, and no availability impact. On paper this is a high-priority signal; however, there is no public exploit code identified at time of analysis and no CISA KEV listing, so the unauthenticated reachability claim rests on Adobe's self-reported advisory and is not independently corroborated.
Unauthenticated server-local file exfiltration in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows a remote caller to read any file accessible to the MCP process and have it uploaded to an attacker-controlled endpoint. The issue affects only deployments running the HTTP transports (streamable-http or sse) with READ_ONLY_MODE=false, where a request that carries X-Atlassian-Confluence-Url and X-Atlassian-Confluence-Personal-Token but no Authorization header is accepted as a 'pat' identity, so the attacker-chosen Atlassian URL is used to build the attachment client and the confluence_upload_attachment (or Jira attachment) tool accepts an arbitrary server-side file_path. CVSS 3.1 rates it 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) with confidentiality-only impact, a public Docker-based proof of concept was confirmed by the reporter so publicly available exploit code exists, and EPSS is low at 0.30% (23rd percentile) with no confirmed actively exploited (CISA KEV) status; version 0.22.0 fixes the flaw.
Unauthenticated arbitrary file read in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 lets a remote network caller abuse the streamable HTTP transport, which accepts requests carrying no user identity and silently falls back to the operator's global Atlassian credentials, to force the upload_attachment tool to read any file readable by the MCP process and push its contents into an attacker-chosen Jira issue or Confluence page, where the attacker can retrieve them. Exploitation requires the server to be running the streamable HTTP transport, reachable by the attacker, and configured with shared operator credentials - stdio-only deployments and deployments that enforce per-user identity/tokens are not exposed - and impact is confidentiality-only (file exfiltration), with no integrity or availability effect. There is no evidence of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the underlying issue is a path-traversal flaw (CWE-22) fixed in version 0.22.0, and the practical risk is bounded more by who actually deploys this MCP server over the network than by exploit maturity.
MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows an accepted MCP caller to read arbitrary files from the host on which the server runs: the confluence_upload_attachment tool opens a caller-supplied file_path after only converting it with os.path.abspath, with no check that the resolved path stays inside the workspace, and then uploads the contents as a Confluence attachment the caller can download back. The vulnerability is an access-gated, confused-deputy arbitrary-file-read (CWE-22, assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, high confidentiality impact, no integrity or availability impact); exploitation requires an authenticated MCP caller (PR:L), a server older than 0.22.0 configured with Confluence credentials that can write attachments, and a space the attacker can read back - single-user local stdio deployments where the caller already owns the host gain nothing. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is fixed in version 0.22.0.
Arbitrary local file read leading to data exfiltration affects sooperset's MCP Atlassian server (mcp-atlassian) prior to 0.22.0, where the Jira update_issue tool converts a caller-supplied attachments argument into local filesystem paths and passes them to the attachment upload implementation without any workspace confinement. A caller able to invoke the update_issue tool can therefore use the server as a confused deputy, reading arbitrary files (e.g. credentials, config, SSH keys) readable by the server process and attaching their contents to a Jira issue the caller controls, with confidentiality impact only - no write or code execution through this flaw. Exploitation is access-gated: the vendor rates it AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N (8.6), while our independent assessment scores it PR:L/S:U, since a permitted MCP caller and a shared-credential deployment are realistic prerequisites; no public exploit code has been identified at time of analysis.
Path traversal in MCP Atlassian releases prior to 0.22.0 lets a caller of the confluence_upload_attachment MCP tool read arbitrary files readable by the server's OS user and exfiltrate them by pushing them to Confluence as attachments. The upload code path converts a caller-supplied file_path to an absolute path without the workspace confinement that had already been added to the download path (CVE-2026-27825), so relative or absolute traversal sequences escape the intended workspace. The independent assessment scores the flaw CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (confidentiality only, no integrity or availability impact), requiring an authenticated caller with access to the MCP tool; the vendor's advisory scored it 8.6 with PR:N and S:C. No public exploit identified at time of analysis, and instances at 0.22.0 or later are not affected.
MCP Atlassian server versions prior to 0.22.0 allow an authenticated MCP caller to read arbitrary files from the server host by supplying an absolute or traversal path to the file_path argument of the jira_upload_attachment or confluence_upload_attachment tools, whose bytes are then uploaded into Atlassian and can be read back by the same caller. Exploitation is conditional: it requires the server to be deployed in HTTP or multi-user mode (not single-user stdio), a permitted caller able to invoke the upload tools (CVSS PR:L), and shared operator credentials so the exfiltrated content lands where the attacker can retrieve it; impact is confidentiality-focused (C:H) with limited integrity effect (I:L) and no availability impact. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), though EPSS context was not provided; the vendor-released fix is version 0.22.0.
Arbitrary local file read in MCP Atlassian (mcp-atlassian) prior to 0.22.0 allows an authenticated MCP caller who can reach the Jira or Confluence upload_attachment tool over the HTTP-exposed 'streamable-http' transport to supply a traversal or absolute file_path that is not confined to the workspace, causing the server process to read sensitive local files and exfiltrate them as Atlassian attachments. The vendor rates this 8.3 (CVSS 4.0) with PR:L, high confidentiality impact and no integrity or availability impact, consistent with our independent assessment of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Exploitation is limited by prerequisites: working Atlassian upload credentials and tool access must already be held, the HTTP transport must be exposed rather than stdio-only, and reachable data is bounded to files readable by the server process user; no public exploit code was identified at time of analysis and the issue is not listed in CISA KEV.
Arbitrary server-local file read and exfiltration in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 lets an authenticated, low-privileged MCP caller abuse the upload_attachment tool for Confluence or Jira to read files on the server host via a caller-supplied file_path, then retrieve the pages' contents as a normal attachment. The vulnerability is CWE-22 (path traversal): the pre-0.22.0 code only normalized the path with os.path.abspath and performed no workspace confinement, so absolute paths and traversal sequences that escape the working directory are accepted. Impact is confidentiality-only (no write or code execution) and exploitation is conditionally gated - it matters primarily in shared-credential or multi-tenant deployments where a caller's legitimate upload capability exceeds its intended file-read scope; single-user, locally trusted deployments face negligible additional exposure. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the vendor fix is available in version 0.22.0.
MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 lets a low-privileged authenticated MCP caller write attacker-chosen files into the server's working directory, because validate_safe_path defaults its base directory to os.getcwd() and the Confluence attachment call sites omit base_dir. Overwriting an importable Python module in that location can escalate to code execution once the application imports the modified module, and the vector intentionally bypasses the earlier remediation tracked as CVE-2026-27825. Exploitation requires permitted MCP tool access (CVSS vector shows PR:L, i.e. authenticated with low privileges) and a subsequent import or re-import of the overwritten module, so code execution is not immediate; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. The vendor rates this 8.3, while an independent assessment confirms it is a genuine remote-exploitable code-execution path whose real-world priority is moderated by those preconditions.
Arbitrary server-local file disclosure in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 lets an authenticated, permitted Confluence MCP caller read any file accessible to the server process by passing a traversal or absolute path to the upload_attachment tool and receiving the contents back as a published attachment. Exploitation requires only a valid MCP caller session (no user interaction, low privileges per PR:L), and the scope change in the CVSS vector reflects the server process acting as a confused deputy on behalf of the caller, yielding high confidentiality impact with no integrity or availability effect. There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is highest in shared-credential or multi-tenant MCP deployments where the caller is less privileged than the server process, and is low in single-user deployments where the caller already owns the underlying filesystem. Vendor-released patch: 0.22.0.
Authenticated file-write path traversal in the Lantronix web management portal lets a logged-in attacker upload a crafted filename that escapes the intended upload directory and writes arbitrary files to any writable location on the device, a primitive that can be leveraged for remote code execution and results in complete loss of confidentiality, integrity, and availability on the console server. Affected are SLC8000 units below firmware v9.7.0.5, EMG8500/EMG7500 below firmware v9.7.0.1, and all firmware versions of SLB882, SLCx-03, and SLCx-02 (no vendor fix published for those three models). Exploitation requires a valid authenticated session on the network-reachable management portal (CVSS v4.0 PR:H, AV:N), so exposure is highest where the portal is internet-facing or reachable from untrusted segments; there is no public exploit identified at time of analysis and the issue is not listed on CISA KEV, but the assessed impact and the embedded out-of-band role of these devices justify treating it as high priority.
Unauthenticated remote attackers can completely compromise the web management portal of Lantronix console servers, reading sensitive configuration files, writing files to arbitrary filesystem locations, and ultimately achieving remote code execution. Affected are SLC8000 units below firmware 9.7.0.5, EMG8500/EMG7500 units below firmware 9.7.0.1, and SLB882/SLCx-03/SLCx-02 devices, which are vulnerable in every firmware version released to date. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; vendor CVSS 4.0 score 10.0) requires nothing more than HTTP reachability to the portal upload endpoint - no credentials, user interaction or non-default settings - and exploitation yields total loss of confidentiality, integrity and availability on the device plus potential impact on serial-connected downstream equipment; no public exploit code has been identified at time of analysis, though a third-party technical writeup accompanies the disclosure.
Unconfined template path resolution in the Vector observability pipeline's file sink allows attacker-influenced event data to create or overwrite files anywhere the Vector process has write access, affecting versions 0.10.0 up to but not including 0.57.0. Because the rendered path is opened without confinement to an intended directory, a crafted event field can supply an absolute path or '../' traversal, and Vector will even create the missing parent directories before writing. No public exploit code has been identified at time of analysis and the flaw is not in CISA KEV, but impact is severe (CVSS 4.0 base 9.3 / assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) and escalates to code execution when the overwritten target is a scheduled task, authorization file, or subsequently executed script. Real-world risk is configuration-gated: it requires a file sink whose path template interpolates an untrusted event field, and the damage ceiling tracks the privileges Vector runs with.
Unauthenticated attackers who can reach the file-upload interface of Check Point Management Server can combine directory traversal with a malicious file upload to place and execute arbitrary scripts, resulting in full loss of confidentiality, integrity, and availability on the management server (vendor-assigned CVSS 9.8, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vulnerability is network-exploitable with no authentication and no user interaction, so the decisive real-world factor is exposure: these servers are normally confined to internal administrative networks, and risk rises sharply if the affected upload endpoint is reachable from an untrusted network. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and affected version ranges are not enumerated in the available data.
Unauthenticated path traversal in the Dancer2 Perl web framework (versions 2.1.0 up to but not including 2.2.0) lets a remote attacker read arbitrary files that the worker process can access, including configuration files such as config.yml stored above public_dir. The flaw only manifests in a non-default deployment where the application names File in its route_handlers configuration and sets static_handler to 0 - because the default static handler refuses dot segments before the File route executes; applications left at defaults are not affected. The vendor has released Dancer2 2.2.0 with a containment fix, EPSS is low (0.19%, 8th percentile), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Directory traversal in Bisheng 2.3.0, 2.4.0, and 2.4.0-beta1 allows unauthenticated remote attackers to read arbitrary files from the server filesystem through the Linsight task-execution endpoint implemented in src/backend/bisheng/linsight/domain/task_exec.py. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates no authentication or user interaction is required against default configurations, with impact bounded to confidentiality - disclosure only, no code execution or file modification. Publicly available exploit code exists (SSVC exploitation status 'poc'; a public gist accompanies the report), but the vulnerability is not confirmed actively exploited (no CISA KEV entry), and EPSS is low at 0.33% (24th percentile), so priority should be driven by whether an organization actually exposes a Bisheng instance to untrusted networks.
Directory traversal in Agent Zero 1.7 through 1.10 lets the AI agent's file-browser component read files anywhere on the host, because FileBrowser is initialized with the host root as its workspace rather than a confined sandbox. The CVSS 3.1 vector is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), which models unauthenticated network access, but the practical risk is gated by whether the Agent Zero UI is exposed to untrusted networks; Agent Zero is often a local single-operator tool, so the AV:N/PR:N rating only applies when that interface is deliberately reachable without an authentication layer. At time of analysis there is no confirmed active exploitation (no CISA KEV entry) and no public exploit identified at time of analysis, and EPSS is 0.33% (24th percentile), indicating low predicted exploitation activity; reference material consists of a GitHub issue and a gist.
Directory traversal in Bisheng 2.3.0, 2.4.0, and 2.4.0-beta1 lets a remote attacker use crafted filename/path input to break out of the intended download/cache directory through the save_download_file routine (src/backend/bisheng/core/cache/utils.py:290), yielding arbitrary file read and write with a CVSS 3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). The vector indicates an unauthenticated, network-reachable attack with no user interaction, though the practical limiting factor is whether the API route that reaches save_download_file is exposed without a login - defenders should verify that against their own deployment before assuming unauthenticated reachability. Exploitation status: no public exploit identified at time of analysis, and there is no CISA KEV entry; EPSS is 0.33% (24th percentile), so mass exploitation is not currently expected, but the impact per successful attack is severe given the high confidentiality and integrity ratings and the absence of any availability impact.
Directory traversal in agent-zero 1.7 through 1.10 allows remote attackers to write files to arbitrary locations outside the intended file-browser directory via the save_file_b64 method, with the evaluated CVSS vector indicating PR:N/UI:N and high integrity impact according to the authoritative assessment. No CISA KEV listing was provided, and no public exploit identified at time of analysis; EPSS is 0.33% (24th percentile), and the supplied CVSS 3.1 score is 7.5, though the independent assessment shifts the impact from confidentiality to integrity (C:N/I:H/A:N) because exploitation concerns unauthorized file writes rather than reads.
Path traversal in the WatchGuard Fireware OS WebUI management agent lets an authenticated administrator read or list arbitrary files on the local filesystem by submitting a specially crafted management request. Exploitation requires valid WebUI administrator credentials (the highest management privilege on the Firebox), per the assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, so the flaw is remote and low-complexity once the attacker already holds admin access, and the impact is limited to confidentiality (file read/list) with no write, code execution, or availability effect. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the vendor advisory is published at https://psirt.watchguard.com/CVE-2026-13224 and no EPSS score was provided in the available data.
Missing authorization in the wgagent management daemon of WatchGuard Fireware OS allows an authenticated, low-privileged management account - including read-only or guest administrator roles - to crash the daemon and read files accessible to its process by sending a crafted request to the management API. The weakness sits in the daemon's session-initialization function, which fails to enforce proper privilege validation before handling attacker-controlled input; the associated path-traversal class (CWE-22) is what enables the arbitrary file read, while the crash produces a denial-of-service condition against the agent. Exploitation requires a valid management session and network reachability to the management plane (CVSS 4.0: 7.1, PR:L, VA:H, VC:L), so risk concentrates on Fireboxes with exposed or broadly accessible management interfaces, multi-admin/multi-tenant deployments, and environments where guest or read-only admin accounts are provisioned. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Toptech Systems TMS7 and TopHat expose a file export endpoint that lets any network-reachable, unauthenticated attacker submit a single crafted POST request and pull arbitrary database tables out of the system - an information disclosure of the highest severity as scored by CISA ICS (CVSS 10.0), and assessed by our analysis as AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, i.e. confidentiality-only impact with no integrity or availability effect. Affected are deployments of Toptech TMS7 (all versions captured in CPE with a wildcard version) and TopHat, which are OT/ICS fuel-terminal and terminal-automation products typically expected to sit on segmented operational networks; the decisive factor for real-world exploitability is whether the export endpoint is reachable from outside that trusted OT segment, since no authentication, user interaction, or non-default toggle is required. There is no public exploit code identified at time of analysis and the flaw is not listed on CISA KEV, so exposure should be treated as a configuration-and-segmentation problem rather than a confirmed ongoing campaign. Authentication requirements are not in question here: the CVSS vector contains PR:N, so exploitation is unauthenticated.
Path traversal in VLC media player's skins2 ThemeLoader (before 3.0.24) allows attackers to write arbitrary files with VLC user privileges by crafting a malicious .vlt skin archive, enabling code execution through Lua script injection. Exploitation requires the victim to run the non-default skins2 interface and open the malicious skin, so local user interaction and social engineering are needed. No public exploit code has been identified at time of analysis, and the CVSS 4.0 score is 8.5 (assessed as CVSS 3.1 7.8 due to local attack vector and user interaction).
IBM DataStage on Cloud Pak for Data 5.4.0.0 contains a path traversal flaw in its archive extraction routine that lets a remote attacker with a valid authenticated account write files outside the intended destination directory and ultimately execute arbitrary code with the privileges of the affected service (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H). The root cause is CWE-22 improper limitation of a pathname to a restricted directory, commonly known as an archive 'zip-slip' condition, where crafted entries in an uploaded archive escape the extraction root. Authentication is mandatory, so this is not an unauthenticated flaw; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the realistic risk is concentrated in enterprise Cloud Pak for Data deployments where the attacker already holds platform credentials or a foothold.
Path traversal in IBM Guardium Data Protection 12.2's Datasource REST component allows authenticated remote attackers with low privileges to delete arbitrary files, causing denial of service and integrity impact. The flaw requires network access to the REST API and valid credentials (CVSS PR:L), with no user interaction. No public exploit code or active exploitation has been identified at time of analysis, but a vendor patch is available.
Unauthenticated content and configuration tampering in Marmite's optional built-in development server (all versions through 0.4.2) lets any network-reachable attacker create, modify, or overwrite site content and configuration by posting to the /__marmite__/content, /__marmite__/config, and /__marmite__/file/ endpoints, with no credentials or user interaction required. The same handlers pass unsanitized path parameters from handle_create_content and handle_clone_content into filesystem writes, so an attacker can traverse out of the project directory and drop or clobber files elsewhere on the host. Exploitation requires the target to be running `--serve` and reachable over the network - pre-0.4.3 the server bound to 0.0.0.0:8000 by default, and production static sites served by Nginx or Apache are unaffected; no public exploit code was identified at time of analysis, and the vendor released 0.4.3 to fix the issue (loopback-by-default binding plus a documented development-only posture).
Unauthenticated path traversal in Marmite's built-in development server (--serve) lets remote attackers read arbitrary files that the marmite process can access, by submitting percent-encoded '..' sequences that the handle_request function in src/server.rs fails to reject after decoding and path-joining. All versions through 0.4.2 are affected, and exposure is significant because the server previously defaulted to binding 0.0.0.0:8000 (all interfaces) rather than loopback, so any host running --serve on a network-facing address was reachable; the 0.4.3 fix commit narrows the default bind to 127.0.0.1 and labels the server development-only. No public exploit identified at time of analysis and the component is a development-only preview server, but the CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N/VC:H, 8.7) reflects a low-complexity, unauthenticated high-confidentiality read with no integrity or availability impact.
Unauthenticated path traversal in Balbooa Forms (a Joomla extension) before 2.4.3.4 allows remote attackers to exfiltrate local files readable by the Joomla process via crafted upload-field JSON during public form submission. The flaw requires that the target form has both the 'auto reply' and 'attach uploaded files' options enabled, limiting exploitability but still posing high risk given the CVSS 4.0 score of 8.9 and no authentication or user interaction required. No public exploit code has been identified at time of analysis, and no active exploitation has been confirmed via CISA KEV.
Arbitrary directory deletion in Joomla CMS affects versions 4.0.0 through 5.4.8 and 6.0.0 through 6.1.3, where a backend user holding administrator-level privileges (CVSS PR:H) can pass a cache group name containing path-traversal sequences that the file-based caching layer fails to sanitize, causing the cache purge action to remove directories outside the intended cache path. The result is high integrity and availability impact with no confidentiality loss, rated 7.0 under CVSS 4.0 (AV:N/AC:L/PR:H/UI:N/VC:N/VI:H/VA:H) and assessed at CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H by independent analysis. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the high-privilege prerequisite confines realistic risk to insider or compromised-administrator scenarios rather than opportunistic remote attackers.
Local privilege escalation in TeamViewer Full Client and Host on Windows, Linux, and macOS (all versions prior to 15.82) allows an authenticated low-privileged local user to write arbitrary files with SYSTEM/root privileges by sending crafted IPC commands to the locally running privileged TeamViewer service daemon. Successful exploitation yields full compromise of confidentiality, integrity, and availability on the host (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and because the flaw is deterministic rather than a race condition it is reliably triggerable once local access exists. No public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); however, the requirement of only low-privileged local access makes it a valuable post-compromise escalation primitive.
Path traversal in Wireshark's configuration-profile import handler (CWE-22) allows a maliciously crafted profile to write files outside the intended profile directory, crashing the application and potentially achieving code execution in the user's context. Affected releases are Wireshark 4.4.0 through 4.4.18 and 4.6.0 through 4.6.8; the flaw is rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R) and requires the victim to manually import the attacker-supplied profile, so exploitation depends on social engineering rather than a network-facing or automatic trigger. Publicly available exploit code exists and the issue is tracked as wnpa-sec-2026-106, but it is not confirmed as actively exploited (CISA KEV) and EPSS is low at 0.19% (7th percentile), making this a moderate-priority issue rather than an emergency; patched releases 4.4.19 and 4.6.9 are available from the vendor.
Unauthenticated network attackers can exploit a directory traversal flaw in the file-upload feature of Hitachi Energy RTU500 Series CMU firmware to write or overwrite arbitrary files on the device filesystem, potentially modifying device data or disrupting operation. The issue has a CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), reflecting high integrity and availability impact with no confidentiality impact. This is a genuine high-priority issue rather than a high-CVSS-but-low-risk artifact, but no public exploit code or confirmed active exploitation was identified at time of analysis, and practical exposure is limited by the typical OT network isolation of RTU500 substation devices.
Remote authenticated attackers can write files to arbitrary locations in Flowring Agentflow 4.0 via a path traversal flaw in the /WebAgenda/download/uploadFile.jsp endpoint, affecting versions released before March 24, 2023. The vulnerability requires a low-privilege authenticated session and no user interaction, with a CVSS 4.0 base score of 7.1. No public exploit code or active exploitation has been identified at the time of analysis.
Authenticated users holding backup or restore privileges on affected FreePBX deployments can achieve remote code execution through the backup Module on versions prior to 16.0.72 and 17.0.7. Improper path sanitization during backup restore lets a crafted archive place attacker-controlled PHP files directly into the web root, where the FreePBX web server will execute them, giving the attacker full control of the host and, by extension, the underlying Asterisk telephony platform (CVSS:4.0 8.6; independent assessment scores CVSS:3.1 8.8, AV:N/AC:L/PR:L/UI:N with high confidentiality and integrity impact). Exploitation is not pre-authentication: it requires a valid account with sufficient access permissions and/or write access to backup files plus network reachability of the FreePBX administration interface, and no public exploit code has been identified at time of analysis. This is a high-priority issue for internet-exposed or broadly permissioned FreePBX instances rather than a drop-everything emergency, since the primary attack surface is a privileged administrative workflow.
Authenticated remote code execution in FreePBX (versions prior to 16.0.10 and 17.0.5) lets an attacker who possesses a valid, known username abuse the sound-language upload and conversion workflow to write arbitrary files, including malicious PHP, into the web server's document root. The root cause is a path-traversal weakness (CWE-22) in the conversion step where path sanitization is insufficient, and successful exploitation gives full confidentiality, integrity and availability impact on the PBX host (vendor CVSS v4.0 8.7; independent assessment CVSS v3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, so authentication - not user interaction - is the gate). No CISA KEV entry and no public exploit code were identified at time of analysis, meaning this is a high-severity, patch-now issue for PBX administrators rather than a mass-exploitation emergency; practical risk concentrates where FreePBX administrative panels are internet-facing or protected by weak or default operator credentials, and is reduced where the panel is network-segmented.
Archive extraction in the Node.js decompress package allows a crafted archive containing chained symlink entries to resolve file writes outside the intended output directory, because the default decompress(input, output) API relies on lexical path containment checks that the kernel's symlink resolution can bypass. This affects @xhmikosr/decompress before 10.2.2 and before 11.1.4, and the separately maintained but unmaintained kevva/decompress package through 4.2.1, which remains unpatched. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:N, 9.1) indicates unauthenticated remote triggering with high confidentiality and integrity impact; writing outside output can overwrite startup scripts or configuration and escalate to remote code execution, and the flaw is a bypass of the incomplete hardening previously applied for CVE-2026-53486. Exploitation requires the consuming application to extract an attacker-influenced archive on a non-Windows platform (Windows emulates symlinks via hardlinks and does not follow the affected path), and no public exploit code was identified at time of analysis, though the upstream fix ships a regression test that documents the escape technique.
Authenticated path traversal in Apache Karaf before 4.4.12 allows a principal holding the shipped 'manager' role to write attacker-controlled content to arbitrary files writable by the Karaf process, because ConfigRepositoryImpl.update() and createFactoryConfiguration() build the target configuration filename from caller-supplied input without confining the result to ${karaf.etc}. Under Karaf's default command/JMX ACL (org.apache.karaf.command.acl.conf.cfg maps 'update = manager'), this lets a manager-role user overwrite files the same ACL reserves to 'admin' - such as etc/users.properties, etc/*.acl.*.cfg, and etc/org.apache.karaf.management.cfg - and thereby grant themselves the admin role or take over the container. The advisory does not indicate active exploitation, and no public exploit code has been identified at time of analysis; EPSS is 0.17% (6th percentile), indicating low predicted exploitation, while published scoring (CVSS 9.8, PR:N) is more severe than this assessment, which requires an authenticated manager-role principal (PR:L) on a deployment that exposes Karaf management and grants manager to non-admins.
Path traversal in Flatpak's app deployment handling of the exported files/etc directory allows a malicious Flatpak application to empty or replace host files such as /etc/passwd, /etc/group, /etc/machine-id, or /etc/resolv.conf with a symlink when that app is installed or upgraded; on system-wide installations the write is carried out as root. Exploitation is gated on user interaction: the victim must choose to install or upgrade the attacker-supplied app from an untrusted source (CVSS 3.1 base 7.1, AV:N/AC:L/PR:N/UI:R with high availability and low integrity impact), making this a genuine but moderate-priority integrity/availability issue rather than a critical remote code execution flaw. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Path traversal in Flatpak's handling of the export/bin directory during application deployment allows a malicious Flatpak app to delete attacker-chosen files outside the deployment directory when that app is installed or upgraded; on system-wide installations the deletions are carried out with root privileges, so a crafted package can remove arbitrary files anywhere the deployer can reach. The flaw affects Flatpak releases before 1.18.4 and is triggered by a user or administrator installing or upgrading an attacker-supplied app, which supplies the required user interaction rather than a network-based trigger; the CVSS vector carries PR:N, so no prior authentication is needed beyond that install action. No public exploit code has been identified at time of analysis and there is no evidence of confirmed active exploitation, though the integrity and availability impact is high (arbitrary file deletion) and the flaw crosses a privilege boundary on system-wide installs.
Authenticated path traversal in Logsign SIEM versions 6.4.101 through 6.4.116 allows a low-privileged user to write arbitrary files to the underlying filesystem. The vulnerability (CWE-22) is reachable over the network via the web/API interface with no user interaction, and the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L) indicates high integrity impact and low availability impact but no confidentiality impact, consistent with an arbitrary file write primitive rather than file read. No public exploit code has been identified at time of analysis, and the issue is fixed in version 6.4.117; the vendor advisory is available via Turkish CERT (TR-26-1202). EPSS score was not provided.
Path traversal in the btrfs storage driver of Canonical LXD 4.0.2 and later allows an authenticated client that holds project-scoped permission to create instances to delete arbitrary files on the host as root by supplying a crafted subvolume path containing ../ sequences, and on hosts whose root filesystem is itself btrfs the same primitive escalates to placing attacker-controlled content at arbitrary host paths for full host compromise. The issue is rated CVSS v3.1 9.6 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H), reflecting a scope-changing breakout from a restricted tenant role into the host root context rather than a CVSS-inflated score, since a legitimate but limited project credential is the only prerequisite. No CISA KEV listing and no public exploit code were identified at time of analysis; vendor fixes are available in LXD 4.0.14, 5.0.10, 5.21.8 and 6.10.
Path traversal in Canonical LXD's Btrfs storage driver allows an authenticated user with instance-creation privileges to escape the intended backup import target and delete or replace arbitrary files and directories on the host as root, by supplying a crafted subvolumes[].path value in backup/optimized_header.yaml during a btrfs 'optimized' backup import. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, 9.9) reflects high confidentiality, integrity and availability impact with a scope change because the traversed write lands outside the LXD daemon's own container boundary; exploitation requires valid low-privilege API credentials and a Btrfs-backed host, not anonymous access. No public exploit code has been identified at time of analysis, and the issue is not confirmed actively exploited (CISA KEV), but the low attack complexity and root-level file-system effect make it a genuine high-priority fix rather than a CVSS-inflated score.
Remote, unauthenticated attackers can retrieve arbitrary local files from Dayforce Payroll by calling its file-download functionality with an absolute path or directory-traversal sequence in the file path parameter, with the server returning the file contents directly in the response. The issue is scored CVSS 4.0 9.2 (vendor/NVD) - network-reachable, low complexity, no privileges or user interaction required, high confidentiality impact, and a scope change to subsequent systems - making payroll data, PII, credentials and configuration secrets the realistic target set. Because vendor contact attempts were unsuccessful, only version R2026.2.0 is confirmed affected and the full version range remains unknown; no public exploit code has been identified at time of analysis.
Path traversal in the Rust-based pacquet package-manager component shipped inside pnpm allows a crafted lockfile to create symlinks and directories outside the project or node_modules boundary during installation. Only pnpm npm-package versions 12.0.0-alpha.0 through 12.0.0-alpha.4 that bundle pacquet are affected, and exploitation requires the victim to explicitly run an install with --trust-lockfile or a frozen lockfile against an attacker-supplied lockfile, so the trust flag that bypasses re-resolution is the enabling condition rather than a remotely reachable flaw. Impact is integrity-focused (CVSS 7.1, CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L), and no public exploit code was identified at time of analysis.
Authenticated directory deletion in the Event Gallery extension for Joomla (svenbluege.de) below version 6.5.0 allows a high-privileged Joomla backend user to supply a traversal payload in the `images` parameter of the `cache.process` clear-cache task and recursively delete any directory the web server account is permitted to write to. The impact is confined to integrity and availability of web-server-writable paths - there is no confidentiality loss (VC:N/SC:N) and no privilege gain beyond the actor's existing administrator-level access, which is the main limiting factor (PR:H), giving a CVSS 4.0 base score of 7.0. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the root cause is a CWE-22 path traversal that accepts unsanitised relative paths before file deletion.
Unauthenticated path traversal in the lomart.fr UP extension for Joomla (versions 5.0.0 through 5.2.0 and 6.0.0 through 6.0.29) allows remote attackers to read files outside the intended plugin directory, exposing configuration files, credentials and other sensitive data under the web root's readable filesystem. The reported CVSS 4.0 score is 9.2, and the independently assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms a confidentiality-only impact with no authentication or user interaction required, while integrity and availability remain unaffected. Real-world risk is governed by deployment scope rather than exploitability: this is a niche third-party Joomla extension, no public exploit was identified at time of analysis, and only sites that have the plugin installed and enabled at an affected version are exposed.
Unauthenticated remote code installation in the lomart.fr 'UP' plugin for Joomla (versions 5.0.0-5.2.0 and 6.0.0-6.0.29) allows remote attackers to write and install arbitrary code on affected sites without authentication, user interaction, or non-default configuration, as reflected in the vendor's CVSS 4.0 base score of 10.0. The flaw is a path traversal (CWE-22) that lets attacker-supplied paths escape the intended directory and place executable content where the web server will run it, giving full compromise of confidentiality, integrity, and availability on the host and follow-on systems. This is a niche, single-vendor Joomla add-on, so exposure depends entirely on whether the plugin is installed and active; no public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing).
Cross-namespace information disclosure in Kyverno before 1.19.1 allows an authenticated low-privilege tenant to read resources from other namespaces by abusing the apiCall context entry in namespaced Policy resources. The attacker crafts percent-encoded dot-segments in urlPath so that Kyverno's validation and execution stages interpret the path inconsistently, ultimately using the admission controller's ServiceAccount credentials to fetch data across the namespace boundary. Exploitation requires the ability to create or modify namespaced Policy resources and a multi-tenant deployment where namespace isolation is the security boundary; no public exploit identified at time of analysis, and a vendor patch is available in Kyverno 1.19.1.
Privilege escalation in Kyverno before 1.19.1 allows an authenticated Kubernetes namespace tenant with Policy/apiCall authoring rights to escape namespace isolation and create objects as Kyverno's admission-controller ServiceAccount. The attacker supplies percent-encoded directory-traversal sequences in the Policy apiCall urlPath to bypass the per-namespace clamp, enabling creation of cluster-wide MutatingWebhookConfiguration objects or PolicyException objects in the kyverno namespace, with a path to cluster-admin escalation. No public exploit identified at time of analysis; vendor patch available in 1.19.1.
Symlink-following flaws in Hugo's theme and module mount confinement allow files outside a project's mount roots to be read during a site build and, via static mounts, published into the public/ output directory. The flaw affects Hugo builds after v0.123.0 and before v0.166.0 for any project that adopts an untrusted theme checked into themes/ or a vendored (non-Go-modules) module containing a symlink at a mount root and then runs a build; the vendor scores this 8.7 (High) under CVSS 4.0, while independent analysis models it as CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N because the site operator must first adopt the malicious theme and execute the build. No public exploit code identified at time of analysis and no KEV listing; a vendor-released patch exists in v0.166.0.
GitPython before 3.1.62 is vulnerable to a path traversal (CWE-22) in Submodule.update() that allows unauthenticated remote attackers to create, populate from a submodule URL, and potentially delete directories outside the repository working tree when an application updates submodules at a non-HEAD (historical) commit. The flaw stems from the `path` field in an untrusted .gitmodules file being used without the _to_relative_path() containment guard that is applied in add() and move(). Exploitation requires an application flow that checks out submodules at a historical commit and an attacker-controlled repository; the standard clone-then-update flow re-derives the path from a canonical tree lookup and is not affected. No public exploit code or confirmed active exploitation (CISA KEV) exists at time of analysis, and the independent assessment rates real-world priority as low-to-medium despite the vendor's CVSS 4.0 score of 8.7.
Remote code execution via arbitrary file write affects Budibase Server versions before 3.45.0. An authenticated attacker holding the BUILDER role can upload a crafted ZIP to the PWA icon upload endpoint that exploits missing symlink validation during extraction, using leaf symlink entries followed by duplicate file entries to overwrite arbitrary files as root. This allows root-level code execution; no public exploit code has been identified at time of analysis, and the vulnerability is not reported as actively exploited.
Authenticated path traversal in SiYuan before v3.8.4 enables an administrator to write arbitrary files and create directory trees outside the workspace boundary via the setNotebookIcon endpoint. By injecting ../ sequences in the notebook parameter, the kernel process can write conf.json and other files to any location the process account can access. Exploitation requires a valid administrator session, so the realistic threat is a malicious or compromised admin rather than an anonymous remote attacker; no public exploit code has been identified, and CISA KEV does not list this issue.
Path traversal in the checkoutRepo endpoint of SiYuan (siyuan-note:siyuan) before v3.8.4 lets an authenticated administrator supply a sessionID parameter containing ../ sequences and overwrite JSON files in pre-existing directories that the SiYuan kernel can already write to, including locations outside the workspace. Integrity impact is high (CVSS 4.0 base 8.3; assessed CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L) but there is no confidentiality impact, no ability to create new files or write non-JSON content, and the PR:H requirement confines realistic abuse to a rogue or compromised administrator rather than an opportunistic remote attacker. No public exploit identified at time of analysis, and the issue is assessed as a moderate, not top-tier, priority.
Path traversal in SiYuan's exportBrowserHTML endpoint lets an authenticated administrator write attacker-controlled HTML into an index.html file outside the workspace directory, affecting all releases before v3.8.4. By supplying a folder parameter containing traversal sequences (such as ../../), an attacker with administrator privileges can overwrite any pre-existing, kernel-writable index.html location, achieving stored cross-site scripting or defacing the workspace. The issue is rated 8.3 (CVSS 4.0) with high integrity impact and low availability impact, requires high privileges (PR:H) and no user interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis; upgrading to v3.8.4 resolves it.
Sensitive local file disclosure in OpenClaw before 2026.8.1 lets a low-privileged caller (PR:L per the CVSS vector, not fully anonymous) smuggle an unvalidated absolute host path past sandbox path validation by supplying structured message attachments that carry multiple 'source' fields, hiding the disallowed path behind an allowed attachment source. When the Telegram delivery channel is configured and active, the agent then reads the referenced host file and relays it out through that channel, giving the attacker high-confidentiality read access to files that policy would otherwise reject. There is no code execution, file modification, or denial of service; EPSS and KEV data are not provided, and no public exploit code has been identified at time of analysis. The vendor has released a fix, and exploitation requires both a message-submission-capable attacker and an OpenClaw deployment that uses Telegram delivery.
Authenticated path traversal in Laranode before 1.2.1 lets any tenant holding a valid account and file manager access write arbitrary files outside their own home directory via the POST /filemanager/upload-file endpoint, including dropping PHP files into other tenants' web roots for code execution as those tenants. The endpoint built its destination as '/home/' + systemUsername + '/' + user-supplied path with no normalization or containment, so a low-complexity traversal request is sufficient on multi-tenant hosts where the web server interprets the written PHP; vendor CVSS 4.0 rates this 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) equally reflects cross-tenant scope change. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV entry); exploitation requires authentication, so single-tenant installations limit the blast radius to the attacker's own account.
Authenticated administrators of ClipBucket v5 who hold the manage_template_access permission can abuse a path traversal in the admin template editor (template_editor.php) to write attacker-controlled PHP files outside the intended styles/layout directory and have them executed as the web server user, yielding remote code execution on all versions before 5.5.3-#197. Publicly available exploit code exists (a HackMD writeup linked from the CVE record), and the vendor has released a fix in commit f31de49b and release tag 5.5.3-#197; the bug is access-gated by the administrator privilege and permission requirement (CVSS 4.0 base 8.6, PR:H), and there is no confirmed active exploitation in CISA KEV. This is a genuine but access-gated risk that primarily matters where multiple admin accounts exist or admin credentials are weak or reused.
GLPI 11.0.0 through 11.0.7 allows an authenticated attacker holding the form-administration privilege to achieve remote code execution by importing a crafted form with an illustration or scene identifier containing path-traversal sequences, causing a file to be written outside the intended custom-asset directory and into a servable or executable location. The CVSS 4.0 base score is 9.4 (Critical), and exploitation requires an authenticated admin session (PR:H) with no user interaction. No public exploit code has been identified at time of analysis; the vendor has released version 11.0.8 to fix the issue.
Insufficient path validation in GLPI's profile-picture update flow lets any authenticated user - including ordinary self-service accounts with no administrative rights - force the application to delete an attacker-selected file on the server's filesystem. Affected releases are GLPI 10.0.0 through 10.0.25 and 11.0.x before 11.0.8; the flaw is fixed in 10.0.26 and 11.0.8. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the CVSS 4.0 base score of 8.5 reflects a remote (AV:N), low-complexity (AC:L) attack with high integrity and availability impact once a valid low-privilege session (PR:L) is obtained.
Authenticated path traversal in the websocket/long-polling session handling of Zammad 7.0.2 and 7.1.0 allows a low-privilege logged-in user to delete arbitrary files and directories on the server with a single crafted request. The client-supplied session (client) identifier is insufficiently validated before being interpolated into internal filesystem paths, so traversal sequences escape the session storage directory - but only on instances using the default file-based session store, since Redis-backed deployments are not affected. Confirmed impact is integrity and availability loss (arbitrary deletion, no read/exfiltration per the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H); there is no confirmed active exploitation (CISA SSVC exploitation: none) and no public exploit identified at time of analysis, though the flaw is fully automatable. Note that the published CVSS 4.0 score of 8.8 carries PR:N, which overstates ease of access - the independent assessment confirms authentication is mandatory.
Local file inclusion in InvoicePlane before 1.7.2 allows an authenticated low-privileged user who can influence the e-invoice xml_id configuration to use path traversal sequences to include an existing .php file from the XMLconfigs helper directory. This is a moderate-priority, not urgent, finding: the advisory establishes local file inclusion, while full code execution would require a separate file-upload or file-write primitive, and no public exploit identified at time of analysis. The issue is fixed in version 1.7.2 via an allowlist on xml_id.
Authenticated path traversal in the Universal Connector Oracle Wallet upload component of IBM Guardium Data Protection 12.2 lets a low-privilege remote user write files to arbitrary filesystem locations on the appliance. The attacker must already hold a valid account with access to the Universal Connector upload function (PR:L) and must craft a traversal sequence that lands a file somewhere useful, which is why the vector carries AC:H despite the high confidentiality and integrity impact. Exploitation has not been observed: CISA SSVC records Exploitation as none and there is no public exploit identified at time of analysis, so this is a genuine but moderate-priority issue rather than a widespread emergency - though the 'total' technical impact rating means a successful hit against a misconfigured deployment could be severe.
Unauthenticated remote attackers who can reach an existing publicly shared Briefcase document can abuse unsigned save fields in Zimbra Collaboration Suite's OnlyOffice/Document Editing integration to perform path-traversal writes and execute commands as the zimbra service account. Exploitation is contingent on the non-default OnlyOffice/Document Editing add-on being enabled and on a supported Briefcase document being publicly accessible, so the 9.8 score in the source feed (AV:N/AC:L) is moderated by an independent assessment that rates attack complexity as High (AC:H) given those prerequisites. No public exploit code or confirmed active exploitation was identified at time of analysis, and no patched version could be confirmed from the single Zimbra wiki advisory reference provided.
Path traversal in IBM Guardium Data Protection 12.2 allows a remote attacker holding valid low-privilege credentials (CVSS PR:L) to escape a restricted directory and read sensitive files, delete arbitrary files, or execute arbitrary code on the appliance. The condition is not unauthenticated - it requires network reachability to the Guardium instance plus a legitimate low-privilege account - and attack complexity is rated high (AC:H), so exploitation depends on crafting path inputs that satisfy conditions outside the attacker's full control. No public exploit code has been identified and the flaw is not confirmed actively exploited (no CISA KEV listing), though vendor patch guidance is available and the CVSS score of 7.5 reflects the high confidentiality, integrity and availability impact if the traversal succeeds.
A use-after-free race condition in QEMU's 9pfs (virtfs) passthrough subsystem allows a malicious guest user to escape the shared directory boundary and read or write arbitrary files on the host, potentially achieving code execution as the QEMU process user (VM escape). Only hosts that have enabled 9pfs/virtfs host-directory sharing are exposed, since this is not a default configuration; the attacker must be a local guest user able to issue 9p protocol requests and must win a race between QEMU's main thread and a 9pfs worker thread with concurrent Tlcreate and Twalk requests. No public exploit code or active exploitation telemetry was identified at time of analysis, but the flaw is rated high severity (CVSS 8.8, scope-changed, C:H/I:H/A:H) and affects QEMU packages shipped in Red Hat Enterprise Linux 6 through 10, Red Hat OpenShift Container Platform 4, and related Red Hat products.
PHP code execution on Netgate pfSense Plus and pfSense CE firewalls can be achieved by an authenticated, highly privileged webGUI user who can modify Dashboard widget settings and plant a crafted .widget.php file on the filesystem, then set a widget sequence value containing path traversal so Dashboard index.php include()s and executes that file. The vendor rates this High (CVSS 8.5), while the independent assessment keeps AV:N/AC:H but raises the privilege requirement to PR:H, reflecting that the attacker already needs substantial Dashboard and file-write access; it is not remotely exploitable without authentication. No public exploit or KEV-listed active exploitation was identified in the provided data, and Netgate has released fixed versions.
Path traversal in the HTTP server built into the Botslab G980H dash camera lets anyone already connected to the camera's own WiFi network retrieve files from its removable storage without authentication or user interaction. Readable content includes recordings, images, diagnostic logs and firmware files, which are exactly the artifacts a web server should never expose. CISA's ICS advisory ICSA-26-267-01 tracks the issue as CWE-22 and scores it 7.1 (High), driven entirely by confidentiality impact; proximity is the limiting factor, since the flaw is reachable only from the adjacent network and cannot be triggered from the general internet. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Arbitrary local file and directory deletion on Docmost deployments that use local storage, exploitable by any authenticated low-privileged user. An attacker stores a crafted avatarUrl value that is not confined to the intended avatar directory; when Docmost's avatar cleanup routine later consumes that stored value, it deletes files or directories reachable by the Docmost service account. The issue affects Docmost versions prior to 0.80.1 and is rated CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L) - high integrity impact, low availability impact, no confidentiality loss. There is no public exploit code identified at time of analysis, and exploitation requires a valid account, so risk is concentrated in multi-tenant or shared instances running local storage.
An authenticated Discourse user who can post content can bypass the administrator's `allowed_iframes` subpath restriction and embed iframe content from a path the administrator never authorized, affecting all Discourse releases prior to 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0. The allowlist guard did not treat literal backslashes as path separators after decoding percent-encoded dot segments, so a crafted iframe source passed the subpath check while browser URL normalization resolved the frame outside the permitted path; exploitation requires a victim to view the post and depends on the viewer browser's backslash normalization behavior, consistent with the assessed vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (limited confidentiality and integrity impact, no availability impact, scope change). This is a moderate, non-priority finding - no public exploit identified at time of analysis.
Path traversal in the pulpcore content upload API allows an authenticated user holding only low-privilege file-repository permissions to read arbitrary files accessible to the Pulp server process by submitting a crafted 'file:' URL through the 'file_url' parameter, which is dispatched to the file downloader despite an intended scheme check. Baseline impact is confidentiality loss on the Pulp host; in deployments that include Pulp Container the same flaw escalates to theft of the container registry token signing private key, enabling forged bearer tokens and unauthorized access to every private container repository in the registry. Downstream products embedding pulpcore are affected, including Red Hat Satellite 6, Red Hat Ansible Automation Platform 2, and Red Hat Update Infrastructure 4/5. There is no public exploit identified at time of analysis, and EPSS data was not provided; Red Hat tracks the issue under advisory https://access.redhat.com/security/cve/CVE-2026-90959.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote user holding valid low-privileged credentials to reach files outside the directory the application intends to restrict, producing a high integrity impact (I:H) and a limited availability impact (A:L) while the published vector shows no direct confidentiality loss. Exploitation is remote (AV:N) but rated high complexity (AC:H), meaning success depends on target-specific conditions such as exact file paths or platform state, and it requires a valid account (PR:L) with no user interaction (UI:N). No public exploit code or CISA KEV entry was identified at time of analysis, so this is a real but moderate-priority flaw for unpatched 5.4.0.0 deployments; IBM has published a fix through its support advisory.
IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker with low privileges to execute arbitrary operating system commands by exploiting a path traversal flaw (CWE-22). The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) yields a High severity score of 8.8, reflecting full compromise of confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis, and a vendor patch is available.
Path traversal in Delta Electronics DIAEnergie before 1.11.00.022 allows unauthenticated remote attackers to manipulate file paths on the host, with the CVSS vector indicating high integrity and availability impact but no confidentiality impact, which is consistent with arbitrary file writing, overwriting, or deletion rather than file disclosure. Exploitation is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) and requires only network reachability to the DIAEnergie web application - no credentials, user interaction, or non-default configuration are prerequisites. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so current risk is driven by intrinsic severity and exposure rather than observed exploitation in the wild. The practical threat hinges on exposure: DIAEnergie is a niche industrial energy-management platform typically deployed on segmented OT/enterprise networks, so internet-facing or broadly reachable management interfaces carry the highest risk.
Unauthenticated path traversal in the eesy_ID2WP - Publish InDesign HTML5 WordPress plugin lets any remote attacker read arbitrary files from the host server on any site running version 1.0.3 or earlier. The flaw is reached through the id2wp_path parameter and requires no authentication, no privileges, and no user interaction (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, 7.5 HIGH), with impact limited to confidentiality because the attacker can only retrieve files the web server process itself is permitted to read. No public exploit code has been identified at time of analysis and there is no confirmed actively exploited (CISA KEV) status; the practical risk is opportunistic scanning of WordPress sites that have this niche plugin installed and active.
Authenticated PaperCut NG and PaperCut MF administrators can achieve arbitrary command execution on the underlying host through the Scan-to-Fax component by supplying crafted fax provider settings that contain path-traversal sequences. Exploitation requires a high-privilege admin account (CVSS PR:H) and network reachability to the admin console, and publicly available exploit code exists per the CVSS 4.0 E:P metric; there is no confirmed active exploitation (CISA KEV). The practical risk is concentrated on internet-exposed or compromised admin interfaces rather than opportunistic mass exploitation, making this a serious post-authentication issue rather than a drop-everything emergency.
Authenticated local file inclusion and code execution affects the MasterStudy LMS WordPress plugin in versions from 3.5.29 up to (but not including) 3.7.50, where one display-style setting is used to build a template path without validation. Exploitation requires an authenticated WordPress account with the Contributor role or higher, and turns into arbitrary PHP execution only when a suitable PHP file already exists on the server. Publicly available exploit code exists (WPScan), but there is no confirmed active exploitation (not in CISA KEV) and SSVC rates exploitation as none and non-automatable, making this a high-priority, manually driven issue rather than an emergency; this is especially true for sites that do not permit untrusted users to register at Contributor level or above.
Unauthenticated path traversal in the OpenShift console's /locales/resource.json endpoint allows remote attackers to read arbitrary *.json files from the console pod filesystem by manipulating the lng and ns query parameters, exposing plugin manifests and configuration files, and potentially enabling traversal against registered dynamic-plugin backends. The flaw is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5) and affects Red Hat OpenShift Container Platform 4; no public exploit code has been identified at time of analysis and there is no CISA KEV telemetry, but per the independent assessment this remains a credible remote-attack priority because the endpoint is reachable without credentials and yields high-confidentiality reads. Impact is limited to information disclosure - integrity and availability are not affected per the assessed vector.
Path traversal in Plex Media Server before 1.43.3.10861 lets an attacker who can reach the /system/agents/media/get endpoint read files accessible to the targeted Plex user by supplying ../ sequences in the url parameter. The primary exploitation path requires a valid Plex session token (the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, i.e. authenticated), while a secondary, lower-barrier path lets a LAN-adjacent attacker supply a crafted X-Forwarded-For header that the server trusts as evidence of local context. Read access is nominally bounded by the victim account's permissions, but because the reachable files include the PlexOnlineToken store, successful exploitation escalates from file disclosure to full Plex account and server takeover; no CISA KEV entry or public exploit code appears in the supplied intelligence, and a vendor fix is available in version 1.43.3.10861.
Path traversal in Flatpak's `flatpak build-init` command allows an attacker-controlled SDK container to write arbitrary files outside the developer's working directory when that developer builds against the SDK using both the `--writable-sdk` and `--sdk-extension` flags. The root cause (CWE-22) is that the SDK's declared extension-point `directory` value is resolved through a path helper that does not reject `..` components, so a malicious SDK can steer writes outside the intended build root. The independently assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) is a local, user-interaction-dependent action rather than the remote 9.8 originally submitted; no public exploit code or confirmed active exploitation has been identified at time of analysis, and the attacker must convince the developer to consume a hostile SDK, which severely limits real-world exposure.
Arbitrary host filesystem writes are possible in Flatpak through the extra-data fetch path, and on system-wide installs those writes are performed as root, allowing a malicious or compromised remote to plant attacker-controlled files outside the application sandbox. Exploitation is unauthenticated on the attacker's side (PR:N) but requires user interaction (UI:R): the victim must install or update an application whose manifest uses the xa.extra-data-sources mechanism from a malicious or attacker-controlled repository, and full root-level impact additionally depends on a system install rather than a per-user install. Two defects combine - the files/extra directory is resolved through symlink-following path operations, and blob names taken from xa.extra-data-sources are not sanitized against '..' traversal. There is no public exploit identified at time of analysis and no CISA KEV entry; tracking is available through the upstream advisory GHSA-fqx6-vh4p-42cg and Red Hat's CVE/Bugzilla records.
Unauthenticated path traversal in ManageEngine OpManager and ManageEngine Network Configuration Manager versions before 12.8.671 allows remote attackers to read arbitrary files from the appliance. Because the CVSS vector is PR:N/UI:N (7.5, AV:N/AC:L), no credentials or user interaction are required against a default-reachable deployment - an attacker with network access to the web console can directly request files outside the intended document root and expose configuration, credential, or key material. Impact is confidentiality-only (C:H with I:N/A:N), so the flaw does not permit modification of data or cause denial of service. No public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); the main limiting factor is exposure, since these are typically internal management consoles rather than internet-facing services.
Every desktop application generated by Pake inherits two upstream template defaults that together hand native IPC functionality to untrusted web content, allowing scripts served from any HTTPS origin to invoke the application's own native commands, including download_file. The root cause is a wildcard Tauri capability ("remote": { "urls": ["https://*.*"] } in src-tauri/capabilities/default.json) paired with "withGlobalTauri": true in src-tauri/tauri.conf.json, which places window.__TAURI__.core.invoke() within reach of ordinary page JavaScript; because Tauri's access control list only validates plugin: commands and not commands registered by the application itself via generate_handler!, no permission entry is required to call them. Exploitation is unauthenticated per the assessed vector (PR:N) but requires user interaction (UI:R) - the victim must run the generated app and attacker-controlled JavaScript must execute inside it, whether directly or through third-party analytics, advertising, or a compromised CDN loaded by the wrapped site. Chained with the path traversal tracked separately as CVE-2026-82635, this escalates to arbitrary file write and persistent code execution; no public exploit identified at time of analysis, and the issue is fixed in Pake V3.17.0.
Path traversal in the attachment-handling logic of Foxit PDF Editor and Foxit PDF Reader lets a crafted PDF write an embedded attachment to a directory outside the intended secure area when the document is opened by a local user. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-73) and requires the victim to open the malicious file, so it is user-interaction-gated rather than remotely triggerable, and no authentication is required of the attacker (PR:N). The practical consequence is arbitrary file write under the privileges of the Foxit process, which can escalate into code execution only if the attacker manages to land a file in an execution-relevant location such as a startup or autorun path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS data was not provided.
Insufficient validation of embedded-resource file paths in Foxit PDF Editor and Foxit PDF Reader (CVE-2026-91801) lets an attacker embed traversal sequences in a PDF so that files are written outside their intended location when the document is opened or previewed, with a conditional path from that arbitrary-file-write primitive to code execution. Rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), the issue is a client-side parsing flaw: no authentication is required, but user interaction is mandatory and there is no network-facing or default-service exposure, so risk is bounded to users who process untrusted PDFs. No public exploit identified at time of analysis, and escalation to code execution remains conditional on a viable write target.
Path traversal in ABB Mint Workbench I through version 5876 allows any local user to reach files outside the intended restricted directory, giving high confidentiality impact on the vulnerable host and on a subsequent system while leaving integrity and availability untouched. Exploitation is gated by local access - the CVSS vector specifies AV:L with PR:N and UI:N - so exposure is confined to engineering workstations and commissioning laptops running the affected build rather than servers or internet-facing systems. No public exploit code and no confirmed active exploitation have been identified at time of analysis; ABB has published vendor advisory 9AKK108473A3188.
IBM Financial Transaction Manager (FTM) for Red Hat OpenShift fails to properly validate symbolic links, allowing an authenticated remote user to read files outside the intended path and disclose sensitive information held by the financial platform. The affected code path is reachable across the network (AV:N) but requires a valid FTM session (PR:L), and no public exploit code or confirmed active exploitation has been identified at time of analysis. IBM has published a vendor patch via its support portal; while the vendor-assigned CVSS of 9.9 implies a scope-changing, high-integrity and high-availability impact, independent analysis of the described weakness assesses it as an information-disclosure issue (file read) rather than full system compromise.
Path traversal in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift, affecting builds from 4.0.6.0 through 4.0.10.0 Interim Fix 06 (Operator 4.4.6+20260807.081800), allows an unauthenticated remote attacker (PR:N/UI:N per the CVSS vector) to submit manipulated path input that the product fails to canonicalize and thereby read arbitrary files accessible to the FTM process. The impact is confidentiality-only - no write, code execution, or availability effect - and exploitation requires network reachability to the FTM application endpoint, so internal-only routes or network segmentation materially reduce exposure. A vendor patch is available via IBM's advisory; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low at 0.35% (28th percentile), making this a moderate rather than urgent priority.
Arbitrary server-side code execution in the Plone process is possible through the Classic portlet shipped in plone.app.portlets 5.0.0 through 7.0.1, where user-supplied template and macro fields are assembled into a TALES path expression and then evaluated by the TAL path() helper, allowing a crafted value to be interpreted as a full expression rather than a constrained path. Any authenticated user who can add or edit a Classic portlet can execute code, and under Plone's default role map that includes ordinary registered users on their personal dashboard, so the issue amounts to a post-authentication privilege escalation across the trust boundary between a web user and the server-side Plone process (CVSS 3.1 9.9, scope changed: AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). There is no confirmed active exploitation (no CISA KEV listing) and no public exploit identified at time of analysis, but vendor patches are available in 5.0.8, 6.0.4, and 7.0.2.
Unauthenticated path traversal in Adobe Connect (and its Android mobile app component) lets a remote attacker read files outside the intended access scope on a network-reachable deployment. Per Adobe's CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N, 8.6), the attack needs no credentials and no user interaction, so an internet-exposed default installation is directly targetable; our independent assessment keeps the same network/low-complexity/no-auth/no-interaction profile but treats scope as Unchanged and stresses that impact is limited to reading files accessible to the Connect service account, with no write, no code execution, and no availability impact. On paper this is a high-priority signal; however, there is no public exploit code identified at time of analysis and no CISA KEV listing, so the unauthenticated reachability claim rests on Adobe's self-reported advisory and is not independently corroborated.
Unauthenticated server-local file exfiltration in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows a remote caller to read any file accessible to the MCP process and have it uploaded to an attacker-controlled endpoint. The issue affects only deployments running the HTTP transports (streamable-http or sse) with READ_ONLY_MODE=false, where a request that carries X-Atlassian-Confluence-Url and X-Atlassian-Confluence-Personal-Token but no Authorization header is accepted as a 'pat' identity, so the attacker-chosen Atlassian URL is used to build the attachment client and the confluence_upload_attachment (or Jira attachment) tool accepts an arbitrary server-side file_path. CVSS 3.1 rates it 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) with confidentiality-only impact, a public Docker-based proof of concept was confirmed by the reporter so publicly available exploit code exists, and EPSS is low at 0.30% (23rd percentile) with no confirmed actively exploited (CISA KEV) status; version 0.22.0 fixes the flaw.
Unauthenticated arbitrary file read in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 lets a remote network caller abuse the streamable HTTP transport, which accepts requests carrying no user identity and silently falls back to the operator's global Atlassian credentials, to force the upload_attachment tool to read any file readable by the MCP process and push its contents into an attacker-chosen Jira issue or Confluence page, where the attacker can retrieve them. Exploitation requires the server to be running the streamable HTTP transport, reachable by the attacker, and configured with shared operator credentials - stdio-only deployments and deployments that enforce per-user identity/tokens are not exposed - and impact is confidentiality-only (file exfiltration), with no integrity or availability effect. There is no evidence of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the underlying issue is a path-traversal flaw (CWE-22) fixed in version 0.22.0, and the practical risk is bounded more by who actually deploys this MCP server over the network than by exploit maturity.
MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows an accepted MCP caller to read arbitrary files from the host on which the server runs: the confluence_upload_attachment tool opens a caller-supplied file_path after only converting it with os.path.abspath, with no check that the resolved path stays inside the workspace, and then uploads the contents as a Confluence attachment the caller can download back. The vulnerability is an access-gated, confused-deputy arbitrary-file-read (CWE-22, assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, high confidentiality impact, no integrity or availability impact); exploitation requires an authenticated MCP caller (PR:L), a server older than 0.22.0 configured with Confluence credentials that can write attachments, and a space the attacker can read back - single-user local stdio deployments where the caller already owns the host gain nothing. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is fixed in version 0.22.0.
Arbitrary local file read leading to data exfiltration affects sooperset's MCP Atlassian server (mcp-atlassian) prior to 0.22.0, where the Jira update_issue tool converts a caller-supplied attachments argument into local filesystem paths and passes them to the attachment upload implementation without any workspace confinement. A caller able to invoke the update_issue tool can therefore use the server as a confused deputy, reading arbitrary files (e.g. credentials, config, SSH keys) readable by the server process and attaching their contents to a Jira issue the caller controls, with confidentiality impact only - no write or code execution through this flaw. Exploitation is access-gated: the vendor rates it AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N (8.6), while our independent assessment scores it PR:L/S:U, since a permitted MCP caller and a shared-credential deployment are realistic prerequisites; no public exploit code has been identified at time of analysis.
Path traversal in MCP Atlassian releases prior to 0.22.0 lets a caller of the confluence_upload_attachment MCP tool read arbitrary files readable by the server's OS user and exfiltrate them by pushing them to Confluence as attachments. The upload code path converts a caller-supplied file_path to an absolute path without the workspace confinement that had already been added to the download path (CVE-2026-27825), so relative or absolute traversal sequences escape the intended workspace. The independent assessment scores the flaw CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (confidentiality only, no integrity or availability impact), requiring an authenticated caller with access to the MCP tool; the vendor's advisory scored it 8.6 with PR:N and S:C. No public exploit identified at time of analysis, and instances at 0.22.0 or later are not affected.
MCP Atlassian server versions prior to 0.22.0 allow an authenticated MCP caller to read arbitrary files from the server host by supplying an absolute or traversal path to the file_path argument of the jira_upload_attachment or confluence_upload_attachment tools, whose bytes are then uploaded into Atlassian and can be read back by the same caller. Exploitation is conditional: it requires the server to be deployed in HTTP or multi-user mode (not single-user stdio), a permitted caller able to invoke the upload tools (CVSS PR:L), and shared operator credentials so the exfiltrated content lands where the attacker can retrieve it; impact is confidentiality-focused (C:H) with limited integrity effect (I:L) and no availability impact. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), though EPSS context was not provided; the vendor-released fix is version 0.22.0.
Arbitrary local file read in MCP Atlassian (mcp-atlassian) prior to 0.22.0 allows an authenticated MCP caller who can reach the Jira or Confluence upload_attachment tool over the HTTP-exposed 'streamable-http' transport to supply a traversal or absolute file_path that is not confined to the workspace, causing the server process to read sensitive local files and exfiltrate them as Atlassian attachments. The vendor rates this 8.3 (CVSS 4.0) with PR:L, high confidentiality impact and no integrity or availability impact, consistent with our independent assessment of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Exploitation is limited by prerequisites: working Atlassian upload credentials and tool access must already be held, the HTTP transport must be exposed rather than stdio-only, and reachable data is bounded to files readable by the server process user; no public exploit code was identified at time of analysis and the issue is not listed in CISA KEV.
Arbitrary server-local file read and exfiltration in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 lets an authenticated, low-privileged MCP caller abuse the upload_attachment tool for Confluence or Jira to read files on the server host via a caller-supplied file_path, then retrieve the pages' contents as a normal attachment. The vulnerability is CWE-22 (path traversal): the pre-0.22.0 code only normalized the path with os.path.abspath and performed no workspace confinement, so absolute paths and traversal sequences that escape the working directory are accepted. Impact is confidentiality-only (no write or code execution) and exploitation is conditionally gated - it matters primarily in shared-credential or multi-tenant deployments where a caller's legitimate upload capability exceeds its intended file-read scope; single-user, locally trusted deployments face negligible additional exposure. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the vendor fix is available in version 0.22.0.
MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 lets a low-privileged authenticated MCP caller write attacker-chosen files into the server's working directory, because validate_safe_path defaults its base directory to os.getcwd() and the Confluence attachment call sites omit base_dir. Overwriting an importable Python module in that location can escalate to code execution once the application imports the modified module, and the vector intentionally bypasses the earlier remediation tracked as CVE-2026-27825. Exploitation requires permitted MCP tool access (CVSS vector shows PR:L, i.e. authenticated with low privileges) and a subsequent import or re-import of the overwritten module, so code execution is not immediate; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. The vendor rates this 8.3, while an independent assessment confirms it is a genuine remote-exploitable code-execution path whose real-world priority is moderated by those preconditions.
Arbitrary server-local file disclosure in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 lets an authenticated, permitted Confluence MCP caller read any file accessible to the server process by passing a traversal or absolute path to the upload_attachment tool and receiving the contents back as a published attachment. Exploitation requires only a valid MCP caller session (no user interaction, low privileges per PR:L), and the scope change in the CVSS vector reflects the server process acting as a confused deputy on behalf of the caller, yielding high confidentiality impact with no integrity or availability effect. There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is highest in shared-credential or multi-tenant MCP deployments where the caller is less privileged than the server process, and is low in single-user deployments where the caller already owns the underlying filesystem. Vendor-released patch: 0.22.0.
Authenticated file-write path traversal in the Lantronix web management portal lets a logged-in attacker upload a crafted filename that escapes the intended upload directory and writes arbitrary files to any writable location on the device, a primitive that can be leveraged for remote code execution and results in complete loss of confidentiality, integrity, and availability on the console server. Affected are SLC8000 units below firmware v9.7.0.5, EMG8500/EMG7500 below firmware v9.7.0.1, and all firmware versions of SLB882, SLCx-03, and SLCx-02 (no vendor fix published for those three models). Exploitation requires a valid authenticated session on the network-reachable management portal (CVSS v4.0 PR:H, AV:N), so exposure is highest where the portal is internet-facing or reachable from untrusted segments; there is no public exploit identified at time of analysis and the issue is not listed on CISA KEV, but the assessed impact and the embedded out-of-band role of these devices justify treating it as high priority.
Unauthenticated remote attackers can completely compromise the web management portal of Lantronix console servers, reading sensitive configuration files, writing files to arbitrary filesystem locations, and ultimately achieving remote code execution. Affected are SLC8000 units below firmware 9.7.0.5, EMG8500/EMG7500 units below firmware 9.7.0.1, and SLB882/SLCx-03/SLCx-02 devices, which are vulnerable in every firmware version released to date. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; vendor CVSS 4.0 score 10.0) requires nothing more than HTTP reachability to the portal upload endpoint - no credentials, user interaction or non-default settings - and exploitation yields total loss of confidentiality, integrity and availability on the device plus potential impact on serial-connected downstream equipment; no public exploit code has been identified at time of analysis, though a third-party technical writeup accompanies the disclosure.
Unconfined template path resolution in the Vector observability pipeline's file sink allows attacker-influenced event data to create or overwrite files anywhere the Vector process has write access, affecting versions 0.10.0 up to but not including 0.57.0. Because the rendered path is opened without confinement to an intended directory, a crafted event field can supply an absolute path or '../' traversal, and Vector will even create the missing parent directories before writing. No public exploit code has been identified at time of analysis and the flaw is not in CISA KEV, but impact is severe (CVSS 4.0 base 9.3 / assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) and escalates to code execution when the overwritten target is a scheduled task, authorization file, or subsequently executed script. Real-world risk is configuration-gated: it requires a file sink whose path template interpolates an untrusted event field, and the damage ceiling tracks the privileges Vector runs with.
Unauthenticated attackers who can reach the file-upload interface of Check Point Management Server can combine directory traversal with a malicious file upload to place and execute arbitrary scripts, resulting in full loss of confidentiality, integrity, and availability on the management server (vendor-assigned CVSS 9.8, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vulnerability is network-exploitable with no authentication and no user interaction, so the decisive real-world factor is exposure: these servers are normally confined to internal administrative networks, and risk rises sharply if the affected upload endpoint is reachable from an untrusted network. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and affected version ranges are not enumerated in the available data.
Unauthenticated path traversal in the Dancer2 Perl web framework (versions 2.1.0 up to but not including 2.2.0) lets a remote attacker read arbitrary files that the worker process can access, including configuration files such as config.yml stored above public_dir. The flaw only manifests in a non-default deployment where the application names File in its route_handlers configuration and sets static_handler to 0 - because the default static handler refuses dot segments before the File route executes; applications left at defaults are not affected. The vendor has released Dancer2 2.2.0 with a containment fix, EPSS is low (0.19%, 8th percentile), and no public exploit code or confirmed active exploitation was identified at time of analysis.